Thanks for the clarifications. I'm not sure why plymouth being in the default install matters - it's installed in my machine and I would expect it to run, unless it's broken. As a tester I report when I think something is broken.
In this case, removing "--attach-to-process" from the exec line in the init script brings back the boot splash, removes the warning message and results in plymouthd appearing in the bootchart. (See LP#502494 bug report). Good point about ureadahead - I have checked it out, and it is definitely making the pack file; I see a 30s wait with only ureadahead running once the pack file is in place, which is presumably the time it takes to read it. That means very little reduction in boot time, of course, but it's a ureadahead issue, not plymouth. I think the chart I posted above had some glitch which meant that it was neither reading nor re-tracing the pack file. -- 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
