This bug was fixed in the package mountall - 0.2.5
---------------
mountall (0.2.5) karmic; urgency=low
* Filesystem check progress reporting, including cancellation. LP: 446596.
* When we're waiting for a mountpoint, if a few seconds of inactivity
passes, report what we're waiting for and allow Escape to drop you to
a recovery shell.
* Start usplash for filesystem check progress reporting or when we've
been waiting for more than a few seconds. LP: #431184.
* Hide error removing /forcefsck, people mis-report this as a bug and
don't tell us the error above it.
* Don't call mount.ecryptfs or mount.aufs when adding an entry for
/etc/mtab; these helpers are broken and do not support the -f argument.
This means your passphrase may end up in /etc/mtab, blame them not me.
LP: #431954, #443080.
* Unlink /etc/mtab~ after creating/truncating /etc/mtab and before writing
mtab entries. LP: #431865.
* Stop the recovery shell if the user runs shutdown within it, so we
don't run mountall again. LP: #452196.
* If the root filesystem check fails, we'll need to reboot, so just have
the recovery shell script do that.
* Post-review logic fixes.
-- Scott James Remnant <[email protected]> Tue, 20 Oct 2009 12:19:16
+0100
** Changed in: mountall (Ubuntu Karmic)
Status: Fix Committed => Fix Released
--
mountall tries to resume boot when it shouldn't
https://bugs.launchpad.net/bugs/452196
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
