Red Hat Bugzilla – Bug 219238
Separate graphical setroubleshoot tool from GNOME applet
Last modified: 2007-11-30 17:11:51 EST
I saw an article on NewsForge today about SELinux and saw an setroubleshoot screenshot. I wanted to try this out on my server, so I installed setroubleshoot with yum. I thought running the setroubleshoot tool on my desktop would be as simple as ssh -Xt marvin su -c setroubleshoot but the command wasn't found. So I went to the project's website and found I needed to run sealert. But, this requires GNOME to be running (I run KDE on my desktop). So, I suggest that the graphical tool be separated from the GNOME applet, so that the logs can be analyzed without having GNOME running.
setroubleshoot should work fine with KDE, there is nothing to my knowledge which is so gnome specific as to prevent it from working under KDE. I have tested it under KDE. The sealert component is started by your sesson manager by virture of its desktop file. Unfortunately if you install setroubleshoot and stay in your current session you'll have to start sealert by hand (sealert -s or via the system menu). But the next time you start a session it should be running. There is one known bug, Bug #214516, which prevents the alert icon from appearing under KDE, but this a bug in KDE and is affecting several apps.