*** This bug is a duplicate of bug 530779 ***
https://bugs.launchpad.net/bugs/530779
mountall will keep trying to reconnect anyway and with the main loop
fixes, that initial connect goes away
The remaining bug is that sometimes mountall might not prompt for
boredom (but only if plymouth takes >2s to open its socket), or might
not prompt for fsck failure (but only if plymouth takes longer to open
its socket than fsck takes to run)
Both of those cares are fairly unlikely
And it's far too close to release to muck around with Upstart's ptrace
code
** This bug has been marked a duplicate of bug 530779
init: does not wait for parent to exit when following forks
--
mountall: Could not connect to plymouth
https://bugs.launchpad.net/bugs/551062
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
