Ordering of the splash ahead of emitting rc runlevel level has been done before in Fedora, to properly show shutdown splash to avoid "scary messages".
I have also noticed that there are additional messages generated on the VT through the lifecycle of the machine - that is after lightdm cleared it and shutdown initiated. Therefore I add clearing VT messages before lightdm shutdowns. Instead of introducing a dummy intermediate job to negotiate "whether or not there is a DM to stop", I use the wait-for-state facility and therefore make the following dependency chain: starting rc RUNLEVEL=[016] -> waits to start shutdown-plymouth (if any) -> (stopping plymouth) -> waits to stop lightdm (if any) This also splits plymouth into two jobs, instead of having duplicate / ORed start on, exec & post-start scripts. Semantically it also makes sense, it's two different instances. This also makes "desktop-shutdown" event redundant. To try this out: cd /etc/init; sudo patch -p0 < path/to/patch I have tested it on trusty and have a message-less shutdown. The patch can equally be applied on precise, please test it on the affected precise machines / OEM devices. ** Patch added: "message-less-shutdown.patch" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/967229/+attachment/3924322/+files/message-less-shutdown.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967229 Title: Text mode shown briefly with various "cryptic" texts when logging out or shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/967229/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
