Bug 718442 - Opps when trying to access sealert from KDE under KDM
Summary: Opps when trying to access sealert from KDE under KDM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: 15
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-03 02:50 UTC by Peter Trenholme
Modified: 2011-07-05 17:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-05 17:30:47 UTC
Type: ---


Attachments (Terms of Use)

Description Peter Trenholme 2011-07-03 02:50:48 UTC
Description of problem:
<quote>
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/lib64/python2.7/site-packages/setroubleshoot/browser.py", line 46, in <module>
    import report.io.GTKIO
ImportError: No module named GTKIO
</quote>

Version-Release number of selected component (if applicable):
setroubleshoot-server-3.0.35-1.fc15.x86_64

How reproducible:


Steps to Reproduce:
1.Click the sealert icon in the system tray or run from command line as "sealert -b"
2.
3.
  
Actual results:
Above quoted error message is displayed in a window

Expected results:
Browser window display

Additional info:
I run in "permissive" mode, but like to review every once and a while. (Never found anything unexpected.)

Note that I seldom use GNOME, so I don't know if the problem is specific to the desktop I use, although that seems to me to be unlikely.

Comment 1 Andre Robatino 2011-07-04 04:33:37 UTC
See bug 715373, bug 718454, and bug 718500 - the workaround for now is to install report-gtk manually.


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