I played around with this a little bit. Adding the usplash_down call to /etc/init.d/usplash "stop" fixes the bug to 80%, you still get some seconds of a black text screen with a cursor, until usplash kicks in (the time between killing gdm and calling K01usplash).
Calling usplash_down right before killing gdm doesn't help either, since gdm does too many VT switches, and it looks the same. So in order to avoid patching the gdm, kdm, ldm, and other *wm init scripts, fixing K01usplash is a safe and nonintrusive bandaid for intrepid at least (should look roughly as good/bad as hardy, which wasn't seamless either). -- usplash is not started on shutdown/reboot https://bugs.launchpad.net/bugs/264696 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
