There's another relatively minor bug with ecryptfs. I'm putting it here, though perhaps it should be a different bug report.
When you run "ecryptfs-setup-private" to setup ecryptfs for the logged in user, it creates a directory $HOME/Private on top of which the encrypted data can be mounted.
When the encrypted data is not mounted, that directory contains 2 symlinks:
The second of those symlinks is fine. But the first symlink is broken; the destination ".desktop" file does not exist. Somebody probably forgot to generate it for the distro.
There's another relatively minor bug with ecryptfs. I'm putting it here, though perhaps it should be a different bug report.
When you run "ecryptfs- setup-private" to setup ecryptfs for the logged in user, it creates a directory $HOME/Private on top of which the encrypted data can be mounted.
When the encrypted data is not mounted, that directory contains 2 symlinks:
Access- Your-Private- Data.desktop -> /usr/share/ ecryptfs- utils/ecryptfs- mount-private. desktop ecryptfs- utils/ecryptfs- mount-private. txt
README.txt -> /usr/share/
The second of those symlinks is fine. But the first symlink is broken; the destination ".desktop" file does not exist. Somebody probably forgot to generate it for the distro.