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

Laurent Bigonville bigon at debian.org
Wed Jul 19 09:40:43 UTC 2017


Le 19/07/17 à 11:32, Vincent Lefevre a écrit :
> On 2017-07-19 08:45:31 +0200, Laurent Bigonville wrote:
>> It's maybe started by pam? Do you have libpam-gnome-keyring package
>> installed?
> Yes, this package is installed. I also notice that
> /etc/pam.d/lightdm contains:
>
> -session optional        pam_gnome_keyring.so auto_start
>
> (lightdm is the display manager I'm using.)
>
> If the fact that it's started by pam is normal, I'm still wondering:
>
> 1. why it quits after about 3 minutes;

IIRC, what's happening is:

1) pam start gnome-keyring
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.

You could edit these files and add your session to the list in 
"OnlyShowIn" so the proper commands are called

> 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.



More information about the pkg-gnome-maintainers mailing list