Brad- I committed part of the fix.
The error message is being truncated. That's making this difficult to solve. The fix I committed fixes the error message printing. As for why it thinks you have sessions open, still mounted... What is the output of: cat /proc/mounts when you see this error? -- ecryptfs-setup-private test step fails, bad error message "Sessions still open, not unmounting" "ERROR: Could" https://bugs.launchpad.net/bugs/471725 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 Committed Status in “ecryptfs-utils” package in Ubuntu: Fix Committed Bug description: /home$ ecryptfs-setup-private Enter your login passphrase: Enter your mount passphrase [leave blank to generate one]: Enter your mount passphrase (again): ************************************************************************ YOU SHOULD RECORD YOUR MOUNT PASSPHRASE AND STORE IT IN A SAFE LOCATION. ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase THIS WILL BE REQUIRED IF YOU NEED TO RECOVER YOUR DATA AT A LATER TIME. ************************************************************************ Done configuring. Testing mount/write/umount/read... Sessions still open, not unmounting Sessions still open, not unmounting ERROR: Could /home$ lsof $HOME /home$ version 81-0ubuntu3, incremental Karmic upgrade. _______________________________________________ Mailing list: https://launchpad.net/~ecryptfs Post to : [email protected] Unsubscribe : https://launchpad.net/~ecryptfs More help : https://help.launchpad.net/ListHelp
