Bug 1043134 - Can't suspend when /proc is mounted with hidepid=2
Summary: Can't suspend when /proc is mounted with hidepid=2
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-power-manager
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-12-14 02:49 UTC by Christian Kujau
Modified: 2015-06-29 13:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-29 13:30:53 UTC
Type: Bug

Attachments (Terms of Use)
dmesg from MacBookPro5,5, running 3.11.8-300.fc20 (147.97 KB, text/plain)
2013-12-14 02:49 UTC, Christian Kujau
no flags Details

Description Christian Kujau 2013-12-14 02:49:48 UTC
Created attachment 836548 [details]
dmesg from MacBookPro5,5, running 3.11.8-300.fc20

Description of problem:

Fedora 20 here with XFCE4, when I click on "suspend" on the "Action Buttons" on the top panel[0- the system does not suspend but the screen goes black and the screensaver comes on (locking my screen). No matter how long I wait, the system does not suspend. When unlocked again, a GTK pop-up reads:

 > Failed to run action "Suspend"
 > GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted

The catch: this suspend button works just fine, but I'd like to mount /proc with hidepid=2 and then the suspend button does not work any more. Issuing "sudo pm-suspend" in xfce-terminal does work however, even with hidepid=2

[0] it's a drop down menu with my name on it and lists "lock screen", "switch user", "suspend", "hibernate", "shut down", "restart", "log out"

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

3.11.8-300.fc20.x86_64 (a later kernel won't boot on this system, possibly due to bug 918767 or bug 1022887)

How reproducible:


Steps to Reproduce:
1. mount -o remount,hidepid=2 /proc       (or hidepid=1)
2. Click on "suspend" in xfce4
3. The system does not suspend

Actual results:

The screensaver comes on, the screen locks. After unlocking, an error popup appears:

 > Failed to run action "Suspend"
 > GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted

Expected results:

The system should suspend.

Additional info:

Workaround: use "sudo pm-suspend" to suspend the system when /proc is mounted with hidepid=1 or hidepid=2

Comment 1 Tomasz Torcz 2014-08-17 21:07:27 UTC
Problem is in polkit, see bug #1130796

Comment 2 Fedora End Of Life 2015-05-29 09:59:15 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 3 Fedora End Of Life 2015-06-29 13:30:53 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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