I have used ubuntu-bug, which brought me here. Do you want more information, James?
The symptoms are dramatic: the error message is mountall: cannot connect to plymouth bootchart shows that plymouthd does not start as expected, and the fsck tasks are done without any delay. There may or may not be other error messages: one I got was cannot open session: no such file/directory The machine takes a long time to boot (sometimes over 3 minutes, compared to a normal < 1minute.) Sometimes I get the low-graphics warning, which then starts the desktop in low-graphics mode. Other times the desktop opens in normal resolution despite the error messages. That's what happened in the case illustrated by the bootchart attached..... What is quite clear is that mountall and/or Plymouth are not operating as they were before the update on 12/23; Which is at fault is unclear, but marking both bugs invalid won't make them work. ** Attachment added: "bootchart.png" http://launchpadlibrarian.net/37147789/bootchart.png -- After latest mountall update on Lucid, mountall exits because it cannot connect to Plymouth https://bugs.launchpad.net/bugs/499519 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
