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.