I've linked a branch that clears the vt before lightdm starts up, so any cruft that was echoed out to the terminal will not survive when lightdm stops . This fixes the first bullet you mentioned, and also fixes this problem when you do S3. I've taken the additional step of coloring the text black, but I can take that out if you wish.
As for the second bullet, basically the way to fix this is to make sure that upstart schedules in the plymouth job immediately after lightdm stops and before any other shutdown jobs are scheduled. Or as you mentioned, we could start plymouth before lightdm stops, but I'm not sure how to achieve that.
Hi Steve,
I've linked a branch that clears the vt before lightdm starts up, so any cruft that was echoed out to the terminal will not survive when lightdm stops . This fixes the first bullet you mentioned, and also fixes this problem when you do S3. I've taken the additional step of coloring the text black, but I can take that out if you wish.
As for the second bullet, basically the way to fix this is to make sure that upstart schedules in the plymouth job immediately after lightdm stops and before any other shutdown jobs are scheduled. Or as you mentioned, we could start plymouth before lightdm stops, but I'm not sure how to achieve that.