| Summary: | Opps when trying to access sealert from KDE under KDM | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter Trenholme <PTrenholme> |
| Component: | setroubleshoot | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED CURRENTRELEASE | 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-05 17:30:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
See bug 715373, bug 718454, and bug 718500 - the workaround for now is to install report-gtk manually. |
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.