Bug 232680 - Hibernation or Suspend do not have the necessary permissions
Hibernation or Suspend do not have the necessary permissions
Product: Fedora
Classification: Fedora
Component: ConsoleKit (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Zeuthen
Depends On:
  Show dependency treegraph
Reported: 2007-03-16 12:29 EDT by Aurelien Bompard
Modified: 2013-03-05 22:49 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-02 10:48:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Aurelien Bompard 2007-03-16 12:29:19 EDT
Description of problem:
Clicking on suspend of hibernate in gnome-power-manager brings up the
screensaver. After entering the password, there is a popup saying that HAL did
not manage to suspend/hibernate
In /var/log/messages, I get :

gnome-power-manager: (abompard) Mise en veille de l'ordinateur car l'utilisateur
a cliqué sur mise en veille à partir du menu de la zone de notification
NetworkManager: <info>  Going to sleep. 
gnome-power-manager: (abompard) Permission denied: Not in active session
code='30' quark='g-exec-error-quark'
gnome-power-manager: (abompard) Reprise de l'ordinateur
gnome-power-manager: (abompard) suspend failed

I suspect ConsoleKit since it says "not in active session".

# LANG=C service ConsoleKit status
console-kit-daemon (pid 2154) is running...
# sestatus 
SELinux status:                 disabled

Version-Release number of selected component (if applicable):

How reproducible:
Comment 1 Will Woods 2007-03-30 14:45:08 EDT
If you haven't turned off SELinux, please update selinux-policy-targeted and try
again. This works for me with the current selinux-policy-targeted (2.5.10-2). 
Comment 2 Aurelien Bompard 2007-04-02 10:48:02 EDT
OK, works now (well, my graphic driver doesn't resume, but that's another story).

Note You need to log in before you can comment on or make changes to this bug.