Steve, I ran 'sudo pam-auth-update --force' and checked both "eCryptfs Key/Mount Management" and "ConsoleKit Session Management" which were unchecked.
After rebooting my laptop the ~/Private directory automounted. It was not intentional to keep an old pam.d configuration. I was already using ecyptfs before installing the Ubuntu Private directory feature, so maybe this is the reason why my pam.d setup was different, although I cannot recollect wheter I was given the option to keep the pam.d confirguration or install the package maintainer version during upgrade. Anyway, thank you Steve and Dustin for solving this! Regards, Rune -- Cannot open Private directory after a reboot 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-utils” source package in Ubuntu: Incomplete 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: [EMAIL PROTECTED]:~$ mount.ecryptfs_private keyctl_search: Required key not available When I go to create a key, I get the following message: [EMAIL PROTECTED]:~$ 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
