Comment 10 for bug 507150

This isn't really a duplicate of bug #313812. The home directory is not being unmounted. Bug #313812 concerns the key-ring.

I created a user (zip) with an encrypted home folder, logged in, started a terminal and verified that the encrypted home folder was mounted. I then logged out and logged in as another user with root (sudo) privileges and checked what was mounted. "/home/.ecryptfs/zip/.Private" was still mounted in "/home/zip". I then checked "/dev/shm/ecryptfs-zip-Private" and the value was 1. I then checked what processes owned by "zip" were running.

root@braun-asus:~# ps -u zip
  PID TTY TIME CMD
 4173 ? 00:00:00 systemd
 4183 ? 00:00:00 (sd-pam)
 4199 ? 00:00:00 dbus-daemon
 4329 ? 00:00:00 gvfsd
 4336 ? 00:00:00 gvfsd-fuse
 4369 ? 00:00:00 ibus-daemon
 4416 ? 00:00:00 ibus-dconf
 4465 ? 00:00:00 dconf-service
 4468 ? 00:00:00 ibus-engine-sim
 4618 ? 00:00:00 evolution-sourc
 4633 ? 00:00:00 libertined
 4672 ? 00:00:00 goa-daemon
 4708 ? 00:00:00 goa-identity-se
 4757 ? 00:00:01 mission-control
 4810 ? 00:00:00 gvfs-udisks2-vo
 4825 ? 00:00:00 gvfs-mtp-volume
 4829 ? 00:00:00 gvfs-goa-volume
 4839 ? 00:00:00 gvfs-gphoto2-vo
 4848 ? 00:00:00 gvfs-afc-volume
 4904 ? 00:00:00 gconfd-2
 4911 ? 00:00:00 gvfsd-trash
 4937 ? 00:00:00 gvfsd-burn
 4955 ? 00:00:00 gvfsd-metadata
 4992 ? 00:00:00 zeitgeist-daemo
 5000 ? 00:00:00 zeitgeist-fts
I also checked what files were open by processes owned by "zip" - 164! So it is reasonable that, under these conditions, the encrypted home remained mounted. The problem is that all these process are persisting after log out. I suspect getting rid of them will solve the problem.