[Bug 854068] New: gnome-keyring-daemon does not exit on logout
https://bugzilla.novell.com/show_bug.cgi?id=854068 https://bugzilla.novell.com/show_bug.cgi?id=854068#c0 Summary: gnome-keyring-daemon does not exit on logout Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce@forge.provo.novell.com ReportedBy: olenz@icp.uni-stuttgart.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36 When logging in to an XFCE session and "Start gnome services" is set (in Startup->Advanced), it will start the gnome-keyring-daemon. When logging out again, the process is not ended. On a multi-user system, this has the effect that you get more and more keyring-processes over time. Note that this does not happen when you use a gnome session. Also note that a new gnome-keyring-daemon process is started everytime you login. Reproducible: Always Steps to Reproduce: 1. Make sure "Start GNOME services" is set in your Xfce-Settings. 2. Log in to Xfce. 3. Check that "gnome-keyring-daemon" is running. 4. Log out of Xfce. 5. Check that "gnome-keyring-daemon" is still running. Actual Results: The process stays running even after logout. Expected Results: The process should be terminated when logging out. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=854068 https://bugzilla.novell.com/show_bug.cgi?id=854068#c1 Guido Berhörster <gber@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |olenz@icp.uni-stuttgart.de --- Comment #1 from Guido Berhörster <gber@opensuse.org> 2013-12-13 15:08:39 UTC --- Hmm, it should quit when it receives a Disconnected signal from the DBus session bus, can you check whether a dbus session bus daemon for the user who has logged out is still alive as well? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=854068 https://bugzilla.novell.com/show_bug.cgi?id=854068#c2 Olaf Lenz <olenz@icp.uni-stuttgart.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|olenz@icp.uni-stuttgart.de | --- Comment #2 from Olaf Lenz <olenz@icp.uni-stuttgart.de> 2013-12-16 09:29:15 UTC --- I have just checked it: only the gnome-keyring-daemon process of the users is running. Just to show you some output of "ps" as a proof: cip10:~ # ps aux | grep gnome-keyring cgl13-0+ 741 0.0 0.0 203296 3840 ? Sl Nov29 0:00 gnome-keyring-daemon --start cgl13-0+ 818 0.0 0.0 270904 4268 ? SLl Oct29 0:00 gnome-keyring-daemon --start cgl13-1+ 1680 0.0 0.0 270884 3876 ? Sl Dec02 0:00 gnome-keyring-daemon --start hzaheri 2354 0.0 0.0 203296 3840 ? Sl Nov28 0:00 gnome-keyring-daemon --start cgl13-0+ 3883 0.0 0.0 203296 3172 ? Sl Nov07 0:00 gnome-keyring-daemon --start msahebd+ 5353 0.0 0.0 203320 1908 ? SLl Oct24 0:00 gnome-keyring-daemon --start cgl13-1+ 5539 0.0 0.0 203296 3256 ? Sl Nov07 0:00 gnome-keyring-daemon --start cgl13-0+ 5690 0.0 0.0 203296 3844 ? Sl Nov25 0:00 gnome-keyring-daemon --start msahebd+ 5963 0.0 0.0 203296 3040 ? Sl Oct29 0:00 gnome-keyring-daemon --start cgl13-1+ 7071 0.0 0.0 203292 3844 ? Sl 09:52 0:00 gnome-keyring-daemon --start cgl13-0+ 7177 0.0 0.0 203296 3844 ? Sl Nov26 0:00 gnome-keyring-daemon --start cgl13-0+ 7447 0.0 0.0 203316 3180 ? SLl Oct25 0:00 gnome-keyring-daemon --start cgl13-0+ 7906 0.0 0.0 203324 3412 ? SLl Nov12 0:00 gnome-keyring-daemon --start msahebd+ 8578 0.0 0.0 203320 3188 ? SLl Nov13 0:00 gnome-keyring-daemon --start root 9469 0.0 0.0 7056 868 pts/4 S+ 10:27 0:00 grep --color=auto gnome-keyring msahebd+ 10004 0.0 0.0 203296 3276 ? Sl Nov13 0:00 gnome-keyring-daemon --start msahebd+ 10465 0.0 0.0 203296 3468 ? Sl Nov13 0:00 gnome-keyring-daemon --start cgl13-0+ 10515 0.0 0.0 203320 3432 ? SLl Nov11 0:00 gnome-keyring-daemon --start cgl13-0+ 11686 0.0 0.0 203320 3164 ? SLl Oct25 0:00 gnome-keyring-daemon --start cgl13-0+ 12476 0.0 0.0 203320 3164 ? SLl Nov04 0:00 gnome-keyring-daemon --start kkumar 13796 0.0 0.0 203292 0 ? Sl Oct23 0:00 gnome-keyring-daemon --start cgl13-0+ 14140 0.0 0.0 203296 3260 ? Sl Nov11 0:00 gnome-keyring-daemon --start cgl13-0+ 14229 0.0 0.0 203296 3400 ? Sl Nov05 0:00 gnome-keyring-daemon --start msahebd+ 14903 0.0 0.0 203320 2980 ? SLl Oct30 0:00 gnome-keyring-daemon --start cgl13-0+ 16135 0.0 0.0 203296 3008 ? Sl Nov04 0:00 gnome-keyring-daemon --start msahebd+ 17552 0.0 0.0 203320 2988 ? SLl Oct25 0:00 gnome-keyring-daemon --start msahebd+ 18582 0.0 0.0 203296 0 ? Sl Oct23 0:00 gnome-keyring-daemon --start cgl13-0+ 19374 0.0 0.0 203316 4068 ? SLl Dec03 0:00 gnome-keyring-daemon --start cgl13-0+ 20448 0.0 0.0 203320 4316 ? SLl Dec12 0:00 gnome-keyring-daemon --start cgl13-0+ 21644 0.0 0.0 203316 0 ? SLl Oct21 0:00 gnome-keyring-daemon --start cgl13-0+ 21861 0.0 0.0 203316 0 ? SLl Oct24 0:00 gnome-keyring-daemon --start cgl13-0+ 22583 0.0 0.0 203296 3184 ? Sl Nov08 0:00 gnome-keyring-daemon --start cgl13-0+ 23322 0.0 0.0 203296 3052 ? Sl Oct29 0:00 gnome-keyring-daemon --start cgl13-0+ 23372 0.0 0.0 203292 3036 ? Sl Oct28 0:00 gnome-keyring-daemon --start xduan 25186 0.0 0.0 338496 4560 ? SLl Dec14 0:00 gnome-keyring-daemon --start cgl13-0+ 25587 0.0 0.0 203324 4068 ? SLl Dec12 0:00 gnome-keyring-daemon --start cgl13-0+ 26078 0.0 0.0 203296 3848 ? Sl Nov19 0:00 gnome-keyring-daemon --start cgl13-0+ 26254 0.0 0.0 203296 3844 ? Sl Dec02 0:00 gnome-keyring-daemon --start cgl13-0+ 26344 0.0 0.0 203328 4020 ? SLl Nov21 0:00 gnome-keyring-daemon --start cgl13-0+ 26655 0.0 0.0 203296 3044 ? Sl Oct28 0:00 gnome-keyring-daemon --start cgl13-0+ 27149 0.0 0.0 203320 4088 ? SLl Dec10 0:00 gnome-keyring-daemon --start cgl13-1+ 27529 0.0 0.0 203324 3792 ? SLl Nov22 0:00 gnome-keyring-daemon --start cgl13-0+ 27797 0.0 0.0 338496 4884 ? SLl Oct31 0:00 gnome-keyring-daemon --start cgl13-1+ 29884 0.0 0.0 203300 3840 ? Sl Nov29 0:00 gnome-keyring-daemon --start cgl13-0+ 30187 0.0 0.0 203296 3844 ? Sl Dec02 0:00 gnome-keyring-daemon --start cgl13-0+ 30396 0.0 0.0 203296 4060 ? Sl Nov28 0:00 gnome-keyring-daemon --start cgl13-0+ 30536 0.0 0.0 203296 3036 ? Sl Oct28 0:00 gnome-keyring-daemon --start tkobaya+ 30561 0.0 0.0 203292 0 ? Sl Oct09 0:00 gnome-keyring-daemon --start cgl13-0+ 32227 0.0 0.0 203296 3848 ? Sl Nov21 0:00 gnome-keyring-daemon --start cgl13-0+ 32245 0.0 0.0 203316 0 ? SLl Oct24 0:00 gnome-keyring-daemon --start ttsatso+ 32633 0.0 0.0 203296 3840 ? Sl Dec10 0:00 gnome-keyring-daemon --start cip10:~ # ps -u hzaheri PID TTY TIME CMD 2354 ? 00:00:00 gnome-keyring-d cip10:~ # ps -u kkumar PID TTY TIME CMD 13796 ? 00:00:00 gnome-keyring-d -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=854068 https://bugzilla.novell.com/show_bug.cgi?id=854068#c3 Guido Berhörster <gber@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bnc-team-gnome@forge.provo. | |novell.com --- Comment #3 from Guido Berhörster <gber@opensuse.org> 2013-12-16 14:59:30 UTC --- I just had a quick look at the code, the daemon should quit either if signaled by the GNOME session manager that the session is being ended or in case of Xfce if the DBus session daemon is shutting down on logout resulting in a disconnected signal, see https://git.gnome.org/browse/gnome-keyring/tree/daemon/dbus/gkd-dbus-session... @gnome-team: Any idea why this is not happening? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=854068 https://bugzilla.novell.com/show_bug.cgi?id=854068#c4 --- Comment #4 from Olaf Lenz <olenz@icp.uni-stuttgart.de> 2013-12-16 15:03:53 UTC --- Just out of curiosity: Are you able to reproduce the problem, or is it just our setting? Here it is not just a single machine, but we see it on all of our ~40 machines, but they all use the same configuration. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=854068 https://bugzilla.novell.com/show_bug.cgi?id=854068#c5 --- Comment #5 from Guido Berhörster <gber@opensuse.org> 2013-12-16 15:36:03 UTC --- (In reply to comment #4)
Just out of curiosity: Are you able to reproduce the problem, or is it just our setting? Here it is not just a single machine, but we see it on all of our ~40 machines, but they all use the same configuration.
No, I don't see it on my own machine but I did have issues with the dbus session daemon not terminating on logout. Do you use a non-default configuration? If you use Xfce with LightDM the default PAM configuration will auto-start and unlock gnome-keyring through the corresponding PAM module and if GNOME compatibility mode is enabled in xfce4-session it will read and set up the environment for the session. BTW, as a quick-and-dirty workaround you can kill the leftover daemons from a script started via session-cleanup-script in /etc/lightdm/lightdm.conf. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=854068 https://bugzilla.novell.com/show_bug.cgi?id=854068#c6 Olaf Lenz <olenz@icp.uni-stuttgart.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|gnome-keyring-daemon does |xfce+kdm: |not exit on logout |gnome-keyring-daemon does | |not exit on logout --- Comment #6 from Olaf Lenz <olenz@icp.uni-stuttgart.de> 2013-12-16 16:30:50 UTC --- Ok, that may be a part of the problem: we are using kdm. I have just tested it with gdm. When gdm is used for session management, the keyring disappears when logging out. So apparently the problem is one of the combination of kdm and xfce. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=854068 https://bugzilla.novell.com/show_bug.cgi?id=854068#c7 --- Comment #7 from Guido Berhörster <gber@opensuse.org> 2013-12-16 16:55:06 UTC --- OK, that makes sense, note the PAM configuration /etc/pam.d/common-session: session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm When using kdm, the daemon will not be started on login and the keyring will not be automatically unlocked, rather if you have GNOME compatibility mode enabled in xfce4-session it will exec gnome-keyring-daemon after login with gnome-keyring-daemon --start which is supposed connect to an existing daemon rather than starting one. I'm not sure why it persists and does not immediately exit if no daemon is running, I'll have to look at the code and triage this later. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=854068 https://bugzilla.novell.com/show_bug.cgi?id=854068#c8 Guido Berhörster <gber@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gber@opensuse.org Component|Xfce |GNOME AssignedTo|bnc-team-xfce@forge.provo.n |bnc-team-gnome@forge.provo. |ovell.com |novell.com --- Comment #8 from Guido Berhörster <gber@opensuse.org> 2013-12-20 12:00:58 UTC --- I checked with a gdb, the code from comment#3 is actually never run if there is no gnome-session running, so it does not notice the DBus disconnect. Here is a summary of how it works: If you use any of gdm, lxdm, or lightdm gnome-keyring-daemon will be started upon login via PAM and the keyring will be unlocked with the users password If GNOME compatibility mode is enabled in xfce4-session, the necessary environment variables will be set for the session (i.e. control socket, GPG and SSH agents). On logout the PAM module will send a SIGTERM to the daemon causing it to terminate. If you use any other display manager or don't use the common-session PAM config and either GNOME compatibility mode is enabled in xfce4-session or gnome-keyring-daemon is started by hand, gnome-keyring-daemon will simply not notice if a session ends and keep running. The problem is that the display manager is (ab)used as an indicator to what DE is being used and whether to start gnome-keyring-daemon based on that information. Of course KDE users e.g. might not be happy if gnome-keyring-daemon were started on login by default (although it probably wouldn't do any harm except for resource usage). I'm reassigning this to the gnome-keyring maintainers since this is not really a Xfce-specific problem and I'd like to hear the opinion of the gnome-keyring maintainers on this since I'm not sure what the right fix would be. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com