Bug 719909

Summary: sealert when opening selinux troubleshooter
Product: [Fedora] Fedora Reporter: John Bouras <jlbouras>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dominick.grift, dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-08 12:13:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Bouras 2011-07-08 11:27:08 UTC 
Description of problem:
If I have placed this in the wrong place, then please forgive me. On a scale of 1 to 10, 10 being a Linux guru and 1 being "Linus who?", I am a 2 or 3 at best.

I am on Fedora 15

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


How reproducible:
Everytime


Steps to Reproduce:
1. Click on SELinux Troubleshooter icon or type sealert in a terminal.
2. sealert error popup appears
3.
  
Actual results:


Expected results:
SELinux should start normally

Additional info:
Opps, sealert hit an error!

Traceback (most recent call last):
  File "/usr/bin/sealert", line 692, in <module>
    run_as_dbus_service(username)
  File "/usr/bin/sealert", line 112, in run_as_dbus_service
    app = SEAlert(user, dbus_service.presentation_manager, watch_setroubleshootd=True)
  File "/usr/bin/sealert", line 326, in __init__
    from setroubleshoot.browser import BrowserApplet
  File "/usr/lib/python2.7/site-packages/setroubleshoot/browser.py", line 41, in <module>
    import report.io.GTKIO
ImportError: No module named GTKIO
Comment 1 Daniel Walsh 2011-07-08 12:13:40 UTC 

*** This bug has been marked as a duplicate of bug 715373 ***