Bug 476566

Summary: XFCE login hangs at "starting gnome-keyring-daemon"
Product: [Fedora] Fedora Reporter: Clark Williams <williams>
Component: xfce4-sessionAssignee: Kevin Fenzi <kevin>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: christoph.wickert, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-13 14:57:57 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
ps axf output while xfce login was hung none

Description Clark Williams 2008-12-15 18:27:52 UTC
Description of problem:
Logging into XFCE via GDM started hanging on my rawhide installation (x86_64 on a T60 laptop). The XFCE splash screen would display "Starting gnome-keyring-daemon" and just stop.

Switching to VT2 and logging in via the console, I could see that there were multiple instances of gnome-keyring-daemon started (see attached ps axf output).  Issuing a 'killall gnome-keyring-daemon' would allow the login process to continue and normal operation from that point (something must have started g-k-d after that, because it was running and nm-applet/NetworkManager got keys to join wireless networks properly). 

I eventually set the xfce4-session settings to *not* start gnome-services and was able to successfully login without extra gyrations. 


Version-Release number of selected component (if applicable):
xfce4-session-4.4.2-4.fc10.x86_64

Comment 1 Clark Williams 2008-12-15 18:29:02 UTC
Created attachment 327002 [details]
ps axf output while xfce login was hung

This is the output of 'ps axf' while the login was hung

Comment 2 Kevin Fenzi 2008-12-16 06:01:12 UTC
Strangely, I see here with F10 that there are 2 of them running as well, but everything works ok. 

I wonder if it was always running multiple copies before, but now they are not playing nice together?

Will try and dig some more to see whats going on here.

Comment 3 Clark Williams 2009-01-05 18:16:32 UTC
This went away for a while and now it's back on my rawhide laptop. When I login from gdm, the XFCE splash screen announces that it's starting gnome-power-manager and we stop until I go over to vt2 and issue a 'killall gnome-power-manager'. Startup continues after that and yes, gnome-power-manager is running when the startup sequence finishes.

Comment 4 Clark Williams 2009-01-07 20:31:42 UTC
looks like it's when the "Launch GNOME services on startup" box is checked in the session manager gui that this happens. Unchecking that box gets past the hang. 

Oh and I'm an idiot. The hang occurs when starting gnome-keyring-daemon, not gnome-power-manager (was debugging a g-p-m problem earlier, sorry for the confusion).

Comment 5 Kevin Fenzi 2009-01-11 18:09:27 UTC
Yeah, I can duplicate this here now. 

It looks like gnome-keyring might be setup now to launch via dbus when it's needed, so I guess Xfce shouldn't launch it in it's session anymore. 

And, looking at the 4.6beta2 code for this, it now checks to see if one is running and uses that instead of just trying to start one. 

So, this should go away once the 4.6beta2 stuff lands.

Comment 6 Christoph Wickert 2009-04-17 18:46:10 UTC
A cannot reproduce this bug. Clark, ist this still valid?

Comment 7 Clark Williams 2009-04-17 18:59:16 UTC
I had to drop back to F10 (kernel issue, not XFCE) and haven't gone back to rawhide yet, so I haven't tried duplicating the problem in a while. 

Might as well close it. If I run into it when I go back to rawhide, I'll open another.

Comment 8 Christoph Wickert 2009-04-17 19:29:21 UTC
If you are still on F10, you could try Kevin's repo at
http://www.scrye.com/~kevin/fedora/xfce46/

Comment 9 Kevin Fenzi 2009-05-11 06:23:44 UTC
Any news here? Do you see the issue with 4.6.1 in rawhide?

Comment 10 Clark Williams 2009-05-13 14:37:58 UTC
I have been unable to reproduce this bug in latest rawhide. I'd say close it.

Comment 11 Christoph Wickert 2009-05-13 14:57:57 UTC
Your wish is my command.