After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 731735 - gnome-session-quit fails at everything; not detecting "Running phase"?
gnome-session-quit fails at everything; not detecting "Running phase"?
Status: RESOLVED DUPLICATE of bug 750508
Product: gnome-session
Classification: Core
Component: gnome-session
3.12.x
Other Linux
: Normal major
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-06-16 16:16 UTC by Que Quotion
Modified: 2015-12-27 23:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Que Quotion 2014-06-16 16:16:38 UTC
With gnome-session 3.12.1, gnome-session-quit is unable to do anything.

--logout does nothing at all

--logout --no-prompt gives the error:
WARNING **: Failed to call logout: Logout interface is only available during the Running phase

--poweroff gives the error:
WARNING **: Failed to call Shutdown: Shutdown interface is only available during the Running phase

--reboot gives the error: 
WARNING **: Failed to call Reboot: Reboot interface is only available during the Running phase

--force changes nothing for any command

I suspect the problem is that gnome-session-quit is unable to detect the "Running phase" which I assume to mean the status of gnome-session that is "running" (and it is most certainly running on my machine while I watch gnome-session-quit fail).

Whether or not this is working for you: How is this detection done?
Comment 1 Michael Catanzaro 2015-12-27 23:48:30 UTC
(In reply to Que Quotion from comment #0)
> Whether or not this is working for you: How is this detection done?

The problem is that you previously tried to logout, it failed for some reason, and ever since, gnome-session has transitioned out of the running state. Since logout failed, everything is broken.

So the "some reason" is quite important here.

*** This bug has been marked as a duplicate of bug 750508 ***