xsplash doesn't handle several screens on intel GM965

This sounds like a problem with X rather than xsplash specifically since gdm is also only displaying on one screen.

Daniel,

May be, may be not. Before the introduction of xsplash (around Karmic alpha 3), everything was almost working perfectly : gdm showed up on the external screen. The only problem remaining was that gdm also showed up on the laptop panel even with the lid closed. See this bug report and my comments : https://bugs.launchpad.net/ubuntu/+bug/272669

May be the flaw lies in the intel driver (enabling clone mode by default is not a good choice IMHO).

xsplash doesn't do anything that would affect which monitor gdm shows up on. xsplash just displays on the default screen, something gdm probably also does. If the default screen is not being set correctly xsplash can't really do anything about it.

Daniel,
I don't know which program setup the monitor layout. I found a workaround which confirms that xsplash does not affect monitor layout.

As a workaround, I have added some xrandr commands in gdm init script. The logic is the following one : if an external screen is connected and laptop lid is closed, only the external is used. Otherwise only the laptop panel is used.
Here is the beginning of my customized /etc/gdm/Init/Default. Add lines are between ### BEGIN SETUP SCREEN ### and ### END SETUP SCREEN ###

#!/bin/sh
# Stolen from the debian kdm setup, aren't I sneaky
# Plus a lot of fun stuff added
# -George

PATH=/usr/bin:$PATH
OLD_IFS=$IFS

### BEGIN SETUP SCREEN ###
# Disable TV Output.
xrandr --output TV1 --off
xrandr | grep VGA1 | grep " connected "
if [ "$?" = 0 ]; then
 if grep -q "closed" /proc/acpi/button/lid/LID/state; then
  # VGA1 is connected and the lid is closed"
  xrandr --output VGA1 --auto --output LVDS1 --off
 else
  # VGA1 is connected and the lid is opened"
  xrandr --output LVDS1 --auto --output VGA1 --off
 fi
else
 # VGA1 is disconnected"
 xrandr --output LVDS1 --auto --output VGA1 --off
fi
### END SETUP SCREEN ###

if [ -x '/usr/bin/xsplash' ];
then

You need to adapt the script according to your video card and setup. Use with caution, it may break the video setup.
With this workaround the only I don't see is usplash boot screen.

@Fred: thanks for the workaround

xsplash uses the default monitor, I don't think there is a way to make an informed choice and provide the behavior you would expect, either at xsplash level, or gdm.

@David,

Yes, xsplash and gdm uses the default monitor.
After digging a bit, the default monitor is setup by the kermel modules that enable "Kernel Mode Settings". But I didn't find a way to force a monitor configuration when modules are loaded or just before usplash is started. And I don't know against which packages this bug should be reported (linux kernel ?).
Fixing bug #145501 (it has been fixed upstream) may have a positive impact on this bug.

We actually always use monitor #0 in xsplash right now, because we didn't have API available to query the primary monitor. I'm planning to add the new API to gtk+ in time for Lucid, so xsplash should be able to handle this at that time. But in terms of Karmic, I'm afraid there's nothing really to do right now.

I'd like to reopen this bug, but target it for Lucid.

This package has been removed from Ubuntu. Closing all related bugs.