| Summary: | setroubleshoot-server should Require report-gtk | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jerry James <loganjerry> |
| Component: | setroubleshoot | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | dwalsh, mgrepl, robatino |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-13 12:49:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
The latest libreport-2.0.4-3.fc15 update should have fixed this - see bug 715373. *** This bug has been marked as a duplicate of bug 715373 *** |
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: