Could the be a duplicate of bug #493480? That one seems to be delegated to cryptsetup again, though. The symptoms (/dev/mapper/tmp is created and manual mounitng works) look similar at least.
** Description changed: After an upgrade from karmic to lucid (kubuntu) my luks-encrypted /tmp partition failes to mount during booting the system. - It then gives me the option to boot it manualy and then to continue with booting. The mounting of tmp works, but unfortunatly I'm not able to decrypt my ecrytptfs-encrypted home directory for some reason. + It then gives me the option to boot it manualy and then to continue with booting. The mounting of tmp works, but unfortunatly I'm not able to decrypt my ecrytptfs-encrypted home directory for some reason. On the other hand, when I continue booting without mounting /tmp and then first login to a console (graphical login fails due to missing tmp-directory) and then mount tmp with sudo everything works fine. - Here is the relevant entry of my fstab: /dev/mapper/tmp /tmp ext2 defaults 0 0 And this is what my cryptab looks like: tmp /dev/disk/by-id/ata-WDC_WD800JD-55MUA1_WD-WMAMD5727339-part6 /dev/urandom tmp,cipher=aes-xts-plain,size=256 I'm not sure if this bug is related to https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/544812 so I decided to report it as a new bug for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669466 Title: encrypted /tmp partition doesn't mount during boot after update to lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
