Bug 219238 - Separate graphical setroubleshoot tool from GNOME applet
Summary: Separate graphical setroubleshoot tool from GNOME applet
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: 6
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: John Dennis
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-12 00:46 UTC by Anonymous Coward
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-12-12 01:04:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Anonymous Coward 2006-12-12 00:46:45 UTC
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.

Comment 1 John Dennis 2006-12-12 01:04:39 UTC
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.


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