Bug 509146 - File->Delete All Alerts on Alert List does nothing
Summary: File->Delete All Alerts on Alert List does nothing
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Thomas Liu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-01 14:37 UTC by Jerry Amundson
Modified: 2009-07-01 17:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-01 17:57:06 UTC
Type: ---
Embargoed:

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

Description Jerry Amundson 2009-07-01 14:37:06 UTC 
Description of problem:
File->Delete all alerts on Alert List does nothing

Version-Release number of selected component (if applicable):
setroubleshoot-2.2.10-1.fc12.x86_64

How reproducible:
once

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

Expected results:
alerts deleted

Additional info:
System is on Permissive mode.
Comment 1 Jerry Amundson 2009-07-01 15:03:41 UTC 
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 15:04:28 UTC 
Created attachment 350133 [details]
access not granted window
Comment 3 Jerry Amundson 2009-07-01 15:12:46 UTC 
(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 17:57:06 UTC 
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.

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