In my F8, KDE, SELinux in permissive mode setup, I get a star icon in my systray every now and then, with the tooltip "SELinux AVC denial, click to view". When I click it, nothing is shown, the icon just goes away. The setroubleshoot service is running. setroubleshoot-1.10.7-1.fc8.noarch
If you don't mind could you do me a favor and log in under gnome once and see if the problem goes away. In the past KDE has had numerous problems with the notification applets.
Same thing in GNOME, nothing happens. My GNOME setup is probably somewhat broken though (at least some icons are broken), I didn't even have it installed and just did "smart install gnome-session" to get some packages installed so I could choose GNOME from kdm's session menu and login.
Am also seeing this on a couple of machines - both running KDE. This used to work under F8 (or possibly one of the test releases); I don't know if an update or purging GNOME (and GDM) introduced the issue.
Is this still happening? First of all please make sure you haven't iconified the sealert browser window. If the winodow is already open (even if inconified) clicking the star won't do anything because the application window is already open. If that's not the case then let's verify the sealert process is running in your session, % ps ax | grep sealert should show one sealert process. If it's there good, then click on the star. Is the sealert process still running? Maybe it died for some reason. What happens if you invoke sealert from the Menu? (e.g. Applications-->System Tools-->SELinux Troubleshooter. Does that open the sealert browser window? If you think sealert is dying, let's try and get diagnostic information. Kill any running sealert programs, then run sealert in the foreground via: % sealert -s -V Try to open the browser again, anything in the debug output suspicious?
I had removed all setroubleshoot* packages since they weren't helpful for me and I found that dropping them allowed me to remove a bunch of other packages that I have no use for. But I just reinstalled the whole shebang to verify this, and after "smart install setroubleshoot", start of auditd and setroubleshoot, and logging out and back in, it works. So as far as I'm concerned, feel free to close this bug.
Thank you Ville for your extra effort in verifying this, a lot of folks would not have taken the time. Your help is very much appreciated.
No problem, thank yourself, that's the least I could do after seeing your excellent effort to help in comment 4.