I have tested with two accounts, one old and one newly created. The old account works fine when I login with password. Also manually umounting and mounting Private works fine. However, this account was apparently created before this bug was fixed, so automatic login is hit by comment 60 and 61.
The new account also works fine when I login with password. With automatic login I now get the "Access Your Private Data" symlink and README.txt. Clicking the symlink opens a terminal window asking for my password and then unlocks the Private directory. All seems fine to me. (Intrepid, ecryptfs-utils 53-1ubuntu13) -- Cannot open Private directory after a reboot when "Automatic Login" enabled https://bugs.launchpad.net/bugs/259631 You received this bug notification because you are a member of eCryptfs, which is subscribed to ecryptfs-utils in ubuntu. Status in eCryptfs - Enterprise Cryptographic Filesystem: Fix Released Status in “ecryptfs-utils” source package in Ubuntu: Fix Released Status in ecryptfs-utils in Ubuntu Intrepid: Fix Committed Bug description: Binary package hint: ecryptfs-utils I created an encrypted private directory following the instructions here: https://wiki.ubuntu.com/EncryptedPrivateDirectory Everything worked as it should until I rebooted. When I try to mount my private directory I get the following message: j...@intrepid:~$ mount.ecryptfs_private keyctl_search: Required key not available When I go to create a key, I get the following message: j...@intrepid:~$ ecryptfs-setup-private ERROR: wrapped-passphrase file already exists, use --force to overwrite. I can create a new passphrase if I use the force option, but I shouldn't have to do this everytime I reboot _______________________________________________ Mailing list: https://launchpad.net/~ecryptfs Post to : [email protected] Unsubscribe : https://launchpad.net/~ecryptfs More help : https://help.launchpad.net/ListHelp
