Bug#829698: gnome-keyring lives on after ssh session stops

Laurent Bigonville bigon at debian.org
Wed Jul 19 12:05:42 UTC 2017

Le 19/07/17 à 12:24, Vincent Lefevre a écrit :
> On 2017-07-19 11:40:43 +0200, Laurent Bigonville wrote:
>> IIRC, what's happening is:
>> 1) pam start gnome-keyring
> Is this "/usr/bin/gnome-keyring-daemon --daemonize --login"?
>> 2) during the startup of the session, "/usr/bin/gnome-keyring-daemon --start
>> --components=foo" is called (see /etc/xdg/autostart/gnome-keyring-*) and
>> initialize the process, if the --start command is not called the daemon
>> apparently exists. The thing is that these are only called for
>> "GNOME;Unity;MATE;" sessions, not the others.
> I have XDG_SESSION_DESKTOP=lightdm-xsession, so that I suppose
> that none of these components are started.
> So, that's the reason the daemon exits, I assume. But the question
> is why after 3 minutes and not immediately.

Because on a loaded (or slow) machine, it could take some times between 
the moment pam opens the session and the xdg autostart files are run I 
>>> 2. if I log out quickly after I log in, why it is still running after
>>> the session has ended (up to these 3 minutes).
>> I'm not exactly sure why it's designed like that.
>> With systemd you can fix that by turning the KillUserProcesses to yes in
>> /etc/systemd/logind.conf I think.
> KillUserProcesses=yes would have bad side effects, such as killing
> background computation processes and GNU screen!
You cans start the long running processes using "systemd-run --scope 
--user". But screen should add support to creating a new systemd scope IMHO.

More information about the pkg-gnome-maintainers mailing list