> In the case when plymouthd has been started from > the initramfs, we can be running the bridge straight > away, otherwise it needs to wait for plymouthd to start.
I had assumed that the plymouth-upstart-bridge was designed to wait for plymouth to become available. Otherwise, it will lose events from anything that starts before plymouth does. Granted, that's very little, so *maybe* we don't care about this - in that case, the bridge should just be 'start on started plymouth'. However, otherwise the current start condition is correct and the daemon should simply be fixed to wait for plymouthd to start (probably using inotify). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309617 Title: plymouth-upstart-bridge main process (189) terminated with status 1 at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1309617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
