Created attachment 439995 [details]
patch based on upstream code
Description of problem:
to disable suspend/hibernate. Obviously this isn't a very clean approach. It
would be much better if upower would actually take the policykit privileges
into account for reporting the values to clients, so that gnome-power-prefs,
gnome-session, and other clients would do the right thing and hide the
suspend/hibernate options if the admin (or an OEM) disables those privileges
through a .pkla file, or if the defaults simply change in the future.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. $ cat /var/lib/polkit-1/localauthority/10-vendor.d/20-hibernate.pkla
2. Login as a regulare user
3. Select Shutdown from gnome application menu.
Hibernate option is listed
Hibernate should not be listed
upstream bz - http://bugs.freedesktop.org/show_bug.cgi?id=26473
*** Bug 645462 has been marked as a duplicate of this bug. ***
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. This request has been
proposed for the next release of Red Hat Enterprise Linux.
If you would like it considered as an exception in the
current release, please ask your support representative.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
To allow administrators easily disable the suspend and hibernate actions on the system, DeviceKit-power now checks the PolicyKit authorization before deciding whether an action can be completed.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.