Bug 509146 - File->Delete All Alerts on Alert List does nothing
File->Delete All Alerts on Alert List does nothing
Product: Fedora
Classification: Fedora
Component: setroubleshoot (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Thomas Liu
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-07-01 10:37 EDT by Jerry Amundson
Modified: 2009-07-01 13:57 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-01 13:57:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
access not granted window (44.82 KB, image/png)
2009-07-01 11:04 EDT, Jerry Amundson
no flags Details

  None (edit)
Description Jerry Amundson 2009-07-01 10:37:06 EDT
Description of problem:
File->Delete all alerts on Alert List does nothing

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

How reproducible:

Steps to Reproduce:
1.in SElinux Troubleshooter, click Show all button
2.From menu, File->Delete All Alerts
Actual results:

Expected results:
alerts deleted

Additional info:
System is on Permissive mode.
Comment 1 Jerry Amundson 2009-07-01 11:03:41 EDT
Hmm, I possibly had a denial of some other kind - When I re-opened the gui, there are no alerts, and the message displayed "A program has requested access it has not been granted".
Comment 2 Jerry Amundson 2009-07-01 11:04:28 EDT
Created attachment 350133 [details]
access not granted window
Comment 3 Jerry Amundson 2009-07-01 11:12:46 EDT
(In reply to comment #2)
> Created an attachment (id=350133) [details]
> access not granted window  

Also, the Close button on said window is a no-op in this case.
Comment 4 Thomas Liu 2009-07-01 13:57:06 EDT
I've fixed the close button in the next update.

The Delete All button was deleting alerts from the database but not from the local (GUI) side.  It deletes from both now.

You should see these fixes once 2.2.11 is uploaded.


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