© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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.