** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/41214112/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/41214113/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41214114/Dependencies.txt
**
Sorry, we have to let the X server stop first before plymouth is
started, so there's always going to be a gap here when we've dropped out
to text mode on shutdown. I don't know any way to transition directly
from X to plymouth on shutdown, and I think if Scott knew one it would
already be
Thanks for the info. I just thought since the change from Plymouth to X is
directly possible in Lucid the opposite would be too. Maybe Plymouth can run
the whole time on one console or it is possible to change to a black screen
from X but like I said it is not so important.
With installed
The difference is that plymouth is written to let other programs tell it
that they're taking over the display and to exit leaving a splash screen
up, but the X server is not. (Not to mention the extra layer of
management, the display manager, that's in charge of the X server.)
--
Plymouth isn't
Running Plymouth on a different console would not allow for a seamless
transition; there would be a black screen of a VT switch between
Plymouth and X - and the startup situation would be worse since X would
not be able to inherit the screen contents.
As Steve says, in order to provide a smooth
