Comment 6 for bug 304136

The core bug here is that /lib/init/splash-functions doesn't shut down usplash cleanly, but instead just SIGKILLs it before it has a chance to clean up after itself.

However, upon fixing that I find that the introduction of splash-functions has meant that /etc/init.d/gdm no longer knows how to wait for the active console to change before logging messages, which leaves some visible litter on the console. I'm introducing a new SPLASH_ORIG_CONSOLE environment variable, set by the splash_stop function in splash-functions, which /etc/init.d/gdm can check and use for this purpose.