Bug 720839 - setroubleshoot-server should Require report-gtk
Summary: setroubleshoot-server should Require report-gtk
Keywords:
Status: CLOSED DUPLICATE of bug 715373
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-12 23:16 UTC by Jerry James
Modified: 2011-07-13 12:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-13 12:49:26 UTC
Type: ---


Attachments (Terms of Use)

Description Jerry James 2011-07-12 23:16:47 UTC
Description of problem:
The alert icon appeared, so I clicked on it and got a dialog that says this:

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 41, in <module>
    import report.io.GTKIO
ImportError: No module named GTKIO

The GTKIO module is supplied by report-gtk, but apparently nothing Requires it, since I don't have it installed.  Also, minor nitpick, the word "Oops" has two o's and one p, not the other way around. :-)

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

How reproducible:
Only happened once.

Steps to Reproduce:
1. Make sure report-gtk is not installed.
2. Do something to provoke an AVC denial.
3. Click on the sealert icon.
  
Actual results:
A backtrace for sealert.

Expected results:
The actual AVC denial information.

Additional info:

Comment 1 Andre Robatino 2011-07-13 09:31:09 UTC
The latest libreport-2.0.4-3.fc15 update should have fixed this - see bug 715373.

Comment 2 Daniel Walsh 2011-07-13 12:49:26 UTC

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


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