Hide Forgot
Created attachment 495047 [details] /var/log/messages Description of problem: Logout from the gnome desktop may hang. After clicking "Log Out" in the Log Out dialog, the desktop is shaded and there is a significant delay (~57 seconds) before the gdm greeter appears. There are four of these in /var/log/messages: Apr 26 14:33:29 spruce gnome-session[1351]: WARNING: Client '/org/gnome/SessionManager/Client1' failed to reply before timeout Version-Release number of selected component (if applicable): accountsservice-0.6.9-4.fc15.i686 *** NB: This is under test: Bug 678236 *** accountsservice-libs-0.6.9-4.fc15.i686 gdm-3.0.0-2.fc15.i686 gdm-plugin-fingerprint-3.0.0-2.fc15.i686 gnome-session-3.0.0-1.fc15.i686 gnome-shell-3.0.1-1.fc15.i686 How reproducible: Intermittent. Steps to Reproduce: 1. Select "Log Out" from the user menu. 2. Click "Log Out" in the Log Out menu. Actual results: Logout hangs for about 57 seconds. Desktop is visible, but shaded. Expected results: gdm greeter is displayed. Additional info: Installed from a Live CD. All updates applied. accountsservice-0.6.9-4.fc15.i686 is under test: Bug 678236.
During the hang, the pointer is visible and responsive, caps lock controls the light. The clock updates.
Pressing ctrl-alt-backspace interrupts the hang, after which, the gdm greeter appears.
Would be good to see .xsession-errors, so that we might figure out who Client1 is...
Created attachment 495458 [details] .xsession-errors, the log that knows no time[stamps] :-)
This is difficult to reproduce, but from /var/log/messages, it appears that one such hang occurred with accountsservice-0.6.9-5.fc15.i686 after restarting. ... Apr 27 12:11:33 spruce yum[1779]: Updated: accountsservice-0.6.9-5.fc15.i686 ... Apr 27 12:32:31 spruce rsyslogd: [origin software="rsyslogd" swVersion="5.7.9" x-pid="698" x-info="http://www.rsyslog.com"] start ... Apr 27 12:35:34 spruce gnome-session[1365]: WARNING: Client '/org/gnome/SessionManager/Client1' failed to reply before timeout ...
Hmm, that .xsession-errors is not very useful. Can you add --debug to the Exec line in /usr/share/xsessions/gnome.desktop and retry ?
Created attachment 495787 [details] /var/log/messages with gnome-session --debug on during logout hang Restarted after adding --debug. Logout hung after a few tries. I left the system untouched until the timeout expired and the gdm greeter was displayed.
Created attachment 495788 [details] .xsession-errors with gnome-session --debug during logout hang
Created attachment 495798 [details] /var/log/messages-20110417 This is the oldest log I have. I installed on Apr 12 14:37 from the F15-Beta-Final Live CD. (per times in /var/log/anaconda/) Apr 12 15:22:12 spruce yum[1600]: Updated: gnome-keyring-3.0.0-1.fc15.i686 ... Apr 12 15:22:28 spruce yum[1600]: Updated: gnome-keyring-pam-3.0.0-1.fc15.i686 ... Apr 13 12:08:27 spruce gnome-keyring-daemon[4135]: dbus failure unregistering from session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message b us security policy blocked the reply, the reply timeout expired, or the network connection was broke n. ... Apr 14 09:46:02 spruce kernel: [ 685.394981] gnome-keyring-daemon[1249]: dbus failure unregistering from session: Connection is closed
The system currently has: gnome-keyring-3.0.1-1.fc15.i686 gnome-keyring-pam-3.0.1-1.fc15.i686
After a clean reinstall and full update from the F15-Beta-Live-CD, I reproduced the logout hang on my first attempt. /var/log/messages has one Client1 "failed to reply before timeout" message. The the ISO image has a valid gpg signature, and the install media (CDRW) passes checkisomd5.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping