Okay, it's my best guess at this point that you're suffering from some weird perturbation of Bug #290445.
The fix for that bug should land in intrepid-updates within a day or two. If you'd like to try it now, though, you can try ecryptfs-utils_53-1ubuntu12~ppa1 in my PPA: * https://edge.launchpad.net/~kirkland/+archive You will need to upgrade to this newer version of ecryptfs-utils, and then you'll need to re-run "ecryptfs-setup-private --force". To do that, you might need to move any data you currently have out of ~/Private. :-Dustin -- 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: Invalid 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
