Bug 529709

Summary: gnome-keyring does not exit if started by a pam_stack that does not have a password.
Product: [Fedora] Fedora Reporter: Daniel Walsh <dwalsh>
Component: gnome-keyringAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: rawhideCC: psplicha, rstrode, tbzatek, tsmetana, walters
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-20 15:28:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
This patch returns pam_success if no password is present. none

Description Daniel Walsh 2009-10-19 15:25:01 UTC 
Description of problem:

The fix seems to be to stop starting pam_keyring if no password is provided. Currently it starts the daemon without the --login prompt.  And the gnome-keyring secondary daemon does not complete hooking up to dbus if the --login flag is not passed.  This causes gnome-keyring to not notice when dbus goes away.

This problem causes xguest to be useless since it will not allow you to login if a xguest process is running.  After one login/logout session xguest requires a reboot.  

As an experiment I caused the pam_gnome_keyring go exit pam_session with success if a password is not present, then the gnome-keyring daemon starts properly and exits properly.
Comment 1 Daniel Walsh 2009-10-19 15:29:32 UTC 
Created attachment 365245 [details]
This patch returns pam_success if no password is present.
Comment 2 Yanko Kaneti 2009-10-20 15:14:50 UTC 
*** Bug 529878 has been marked as a duplicate of this bug. ***
Comment 3 Daniel Walsh 2009-10-20 15:28:51 UTC 
I have confirmed this is fixed with gnome-keyring-2.28.1-2

Although pulseaudio is still running for about 10 seconds after logout,  So you can still hit this problem.  We need to fix gdm to not kill gdm-password untill gdm-passwd has finished cleaning up its processes.