Red Hat Bugzilla – Bug 498741
SELinux blocking gnome power manager from applying configuration as default
Last modified: 2010-04-28 14:59:59 EDT
Created attachment 342184 [details]
Description of problem:
On the latest Rawhide (and before), you get an SELinux denial when you click on the "Make Default" button in the gnome power manager (System > Preferences > Power Management).
Version-Release number of selected component (if applicable):
On every Rawhide installation
Steps to Reproduce:
1. Open the Gnome power management GUI
2. Make some changes
3. Click on the "make default" button
No denial :)
See attached denial logs produced when you click on the button.
This is mislabeled /home/Steven/.gconf directory. Execute
restorecon -R -v /home/Steven/.gconf
Should fix it.
Miroslav, since this is likely to happen, I think we should allow it, until we get a better solution for maintaining labels the homedir.
Also make sure this works on NFS and Samba homedirs.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
*** Bug 506395 has been marked as a duplicate of this bug. ***
Fixed in selinux-policy-3.6.12-80.fc11
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. 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 WONTFIX if it remains open with a Fedora
'version' of '11'.
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 prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here: