Description of problem: When presented a button (Turn off memory protection) to address the issue found in bug# 518351 and said button is clicked the response is "Unable to grant access" Version-Release number of selected component (if applicable): How reproducible: I can reproduce this consistently using my laptop (Compaq cq61-324CA) and suspending it. This produces an alert that I can see through SETroubleshoot. When provided the option to turn off memory protection to address the issue, "sealert" comes back with "Unable to grant access" (after I enter the root password) Steps to Reproduce: 1. Suspend the laptop and start it back up (the result is a blank screen which prevents me from doing anything with the machine) 2. Reboot 3. When logged back in open SETroubleshoot. 4. Double click on the entry "SELinux has prevented vbetool from performing unsafe memory operation". 5. Click the button "Turn off memory protection". Actual results: After being prompted for the root password and waiting 10'ish seconds a dialog with the title "Sealert Error" saying "Unable to grant access" Expected results: A dialog confirming that memory protection was turned off, or some indication as to why it wasn't. Additional info:
Fixed in setroubleshoot-2.2.58-1.fc12 yum update setroubleshoot\* --enablerepo=updates-testing
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping