Bug 718500 - Change report-gtk requires to require 0.22 or newer.
Summary: Change report-gtk requires to require 0.22 or newer.
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 16:07 UTC by Susi Lehtola
Modified: 2011-07-05 17:53 UTC (History)
5 users (show)

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


Attachments (Terms of Use)

Description Susi Lehtola 2011-07-03 16:07:05 UTC
I got the following error message:


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


Looks like you're missing a dependency in the RPM.

Comment 1 Andre Robatino 2011-07-04 04:25:13 UTC
Just suggested this in https://bugzilla.redhat.com/show_bug.cgi?id=715373#c74 - the workaround for now is to install report-gtk manually.

Comment 2 Elad Alfassa 2011-07-04 05:34:58 UTC
setroubleshoot has Requires: report-gtk
Because of all the recent libreport vs report mess, I think the solution would be changing it to
Requires: report-gtk>=0.22




-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Elad Alfassa 2011-07-04 05:35:34 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Gavin Romig-Koch 2011-07-05 13:48:08 UTC
Yes, changing setroubleshoot will fix this problem, but simply getting this update

   https://admin.fedoraproject.org/updates/libreport-2.0.4-2.fc15

into f15-updates (now that report-0.22-0 is there) will also fix this problem, and allow a simple 'yum upgrade' to solve this problem, without requiring another update to setroubleshoot.


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