GNOME Bugzilla – Bug 704665
"Logout session" is ignored, but then it actually happens after a 90 sec timeout
Last modified: 2016-07-19 12:05:12 UTC
Hi, this is in fedora 19, 1. When I have some text entered in gedit, and then I procceed to logout my session, a dialog pops up, warning me that there are some unsaved text in gedit and asking my confirmation to close the session and so discard the gedit text. I click the "Log out" button to confirm that I want to exit session regardless of the unsaved text.. and then.. 2. what should happen: the session should be closed. 3. what actually happens: Apparently nothing happens, my action is ignored, but later on I will be kick out of the session after 90 sec from when I initially clicked the logout button. I will attach a video showing the issue.
Created attachment 249769 [details] Video showing the issue
I forgot to add, after reviewing the journalctl log, this is the related error message: Jul 22 09:37:12 fedora19 /etc/gdm/Xsession[3431]: JS LOG: Ignored exception from dbus method: Gio.IOErrorEnum: GDBus.Error:org.gnome.SessionManager.NotInRunning: Logout interface is only available during the Running phase
I've reproduced this in CentOS 7. I filed a CentOS bug report for it here: http://bugs.centos.org/view.php?id=7826 While I can reproduce the exact same symptoms Nelson described, I approached the bug from a different angle in my CentOS bug report. I click on the gedit icon in the logout window which produces different symptoms. My details from my CentOS bug report are: -Type some text in gedit, but don't save it -Click the Gnome "Log Out" menu option -A Log Out/Power Off window pops up with a gedit icon in the middle of it -In the Log Out/Power Off windows click the the gedit icon (do not click the "Cancel", "Restart", "Power Off" or "Log Out" buttons, these buttons won't cause the problem) -After clicking on the gedit icon you're returned to the desktop (if you close gedit now and wait, after five or more minutes you might suddenly get logged out) -Try to log out or power off again. Now these menu items don't do anything other than generate the "GDBus.Error:org.gnome.SessionManager.NotInRunning" log below (i.e. you can no longer logout or power off from the menu!) -A work around fo this issue is to run 'ALT-F2, r' to restart the gnome shell after which the power off/log out menu items work again. //////// This next log is what's generated when I try to log out after I've hung the log out process \\\\\\\\ Nov 3 21:32:57 black gnome-session: JS LOG: Ignored exception from dbus method: Gio.IOErrorEnum: GDBus.Error:org.gnome.SessionManager.NotInRunning: Logout interface is only available during the Running phase //////// Here I ran 'ALT-F2 r' \\\\\\\\ Nov 3 21:33:09 black goa[2343]: secret_password_lookup_sync() returned NULL [goautils.c:210, goa_utils_lookup_credentials_sync()] Nov 3 21:33:10 black goa[2343]: secret_password_lookup_sync() returned NULL [goautils.c:210, goa_utils_lookup_credentials_sync()] Nov 3 21:33:10 black goa[2343]: secret_password_lookup_sync() returned NULL [goautils.c:210, goa_utils_lookup_credentials_sync()] Nov 3 21:33:14 black gnome-session: JS LOG: GNOME Shell started at Mon Nov 03 2014 21:33:14 GMT-0600 (CST) Nov 3 21:33:15 black gnome-session: JS LOG: [impatience] enabled Nov 3 21:33:15 black gnome-session: JS LOG: [impatience] enabled Nov 3 21:33:15 black gnome-session: JS LOG: [impatience] setting new speed: 0.5 Nov 3 21:33:15 black gnome-session: JS LOG: [impatience] setting new speed: 0.5 //////// Gnome shell has finished restarting and is working normally again \\\\\\\\
Great tip on surrecting gnome-shell with the Alt-F2 r combo. Never knew. This indeed brought the Shutdown etc interfaces back from limboland (gnome-shell-3.14.3)
*** Bug 155321 has been marked as a duplicate of this bug. ***
*** Bug 333870 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 750508 ***