** Changed in: ecryptfs-utils (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470030
Title:
"gpg-agent --daemon" stays after login, causing ecryptfs to
I do not know if I will struggle with the bug further,
so I leave here some more notes.
Systemd does not track the process "(pam-sd)" that calls pam_close_session()
https://github.com/systemd/systemd/blob/v229/src/core/execute.c#L895
Sometimes the process reaches setgroups() or setgid() within
** Changed in: gnupg2 (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: gnupg2 (Ubuntu)
Milestone: None => ubuntu-17.02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems that gpg-agent is not the only thing that prevents
encrypted directory from being unmounted. I suspect
that systemd having PID 1 (init) kills systemd --user
while it is preparing to unmount the home directory.
Some observations.
At first I disabled gpg-agent in ~/.gnupg/gpg.conf file.
For the record, you can enable KillUserProcesses=yes in
/etc/systemd/logind.conf to automatically clean up processes which don't
properly terminate upon session stop. It has been tried to make this the
default, but it met heavy opposition, so we won't do that by default.
Reassigning to gnupg2 for
