This bug was fixed in the package mountall - 2.14 --------------- mountall (2.14) lucid; urgency=low
[ Scott James Remnant ] * Flush updates to Plymouth before emitting Upstart events, in case the event kills Plymouth. LP: #559761. * Don't mark a filesystem "nodev" just because it's got "none" in the device column; this will block the "virtual-filesystems" event which is the one that can't use Plymouth to prompt. LP: #507881. * When cancelling in-progress fsck, don't deference the NULL mount record. LP: #562811. * mountall is missing a very important line of code that increases the udev buffer size; without this it's possible we may miss events during busy periods. LP: #561390. [ Steve Langasek ] * If we're not marking all nodev filesystems as virtual, we need to at least mark our placeholder filesystem entries (type=none && dev=none) this way. -- Steve Langasek <steve.langa...@ubuntu.com> Sun, 25 Apr 2010 23:36:01 +0100 ** Changed in: mountall (Ubuntu Lucid) Status: Fix Committed => Fix Released -- [Lucid] fsck cannot be cancelled in Plymouth https://bugs.launchpad.net/bugs/562811 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