This bug was reassigned to mountall because of the following referenced comment on bug #475936:
> Just confirmed that using the test case in lucid, the /tmp directory fails to > be mounted. However, this is because mountall > treats the /tmp directory specially. Varying the /etc/fstab line in either of > two ways is enough to fix this: > - set the 'pass' option to non-zero > - mount it somewhere other than /tmp > > After making either change, mountall successfully mounts the device for me. > I've updated the test case using the first of these options. > (If you believe the mountall behavior is wrong, please file a separate bug report on the mountall package for this.) That's not a bug in cryptsetup. ** Package changed: cryptsetup (Ubuntu) => mountall (Ubuntu) ** Summary changed: - [Karmic, security] Encrypted partitions no longer mounting after upgrade to karmic + [Karmic, security] Encrypted /tmp no longer mounting after upgrade to karmic -- [Karmic, security] Encrypted /tmp no longer mounting after upgrade to karmic https://bugs.launchpad.net/bugs/493480 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
