Please allow for an easy way to disable xsplash

This is not how Jaunty appeared, and I want to see the boot process code as long as possible without having to look at logs and all that later. See: http://ubuntuforums.org/showthread.php?t=1284677

Ignore my comment #2 - that issue more properly addressed here:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/447615

it would also be nice to be able to apt-get remove xsplash without having to remove desktop-switcher ubuntu-desktop ubuntu-netbook-remix etc as well.

On Thu, 2009-10-08 at 20:13 +0000, emarkay wrote:
> This is not how Jaunty appeared, and I want to see the boot process code
> as long as possible without having to look at logs and all that later.
> See: http://ubuntuforums.org/showthread.php?t=1284677

So xsplash is started by gdm; and gdm is started by upstart.

The main thing is that we're running startup scripts in a dependency
order rather than serially.

I get the motivation though, but I don't think xsplash is involved in
solving the issue at all.

-Rob

filed a bug for gdm

I also prefer to have a text boot. Is it possible to add an option to desactivate the xsplash ?

There was no need to open a gdm task there since there was a gdm bug, now to close this bug as duplicate the xsplash task needs to be closed too

Just use that in the patch that hooks xsplash into the gdm startup files:

if grep -qs splash /proc/cmdline && [ -x `/usr/bin/xsplash' ]; then
...

in both /etc/gdm/Init/Default and /etc/gdm/PreSession/Default

Cody: can you update the patch?

17:45 < lool> Keybuk: poke
17:45 < lool> Keybuk: Do you have any issue with adding this check during boot http://bazaar.launchpad.net/~bratsche/gdm/xsplash-check-cmdline/revision/146 ?
17:45 < Keybuk> makes sense to me
17:45 < Keybuk> though why would you want to disable xsplash?
17:46 < Keybuk> you disable usplash because you want to see things going on under it
17:46 < Keybuk> all that goes on under xsplash is the pinwheel
17:46 < lool> Keybuk: Just in case something goes wrong or you simply don't want it
17:46 -!- ior3k [n=quassel@89.152.50.144] has quit [Read error: 110 (Connection timed out)]
17:46 < ion> That would match anything with a ‘splash’ substring.
17:46 < lool> Keybuk: we had the case where it broke and we had no facility to document a workaround, and some people don't like it
17:46 < lool> ion: I suggested adding -w
17:46 -!- mpt [n=mpt@canonical/mpt] has quit [Operation timed out]
17:46 < Keybuk> though strictly speaking, that grep is wrong
17:47 < Keybuk> since that will match root=/dev/mapper/ubuntu-splash-top
17:47 < Keybuk> -w won't help, since - is a word boundary
17:47 < lool> Hmm true, I think gdm was using that though
17:48 < Keybuk> the gdm upstart job reads /proc/cmdline using for
17:48 < Keybuk> random thought
17:48 < Keybuk> if you check for splash in that list and set an ENVVAR, does that end up in the gdm session scripts
17:48 < Keybuk> ie. could you modify /etc/init/gdm.conf, set SPLASH=true at the top
17:48 < lool> we dont need to send an envvar I guess
17:48 < Keybuk> then when it reads the command-line, set SPLASH=false
17:48 -!- tormod [n=tormod@138.131.217.145] has quit ["Ex-Chat"]
17:48 < Keybuk> (or however that should work)
17:49 < Keybuk> then just check that var in the scripts
17:49 < Keybuk> that'd save you a lot of processor time of re-reading /proc/cmdline a dozen times
17:49 < lool> just for ... splash) start xsplash;
17:49 < Keybuk> (well, not that it's much, but each one adds up)

Lucid does not currently use xsplash any more, so the gdmsetup feature is not necessary any more.

xsplash has been obsoleted now.