Description of problem: Trying to troubleshoot using SEalert under KDE is now impossible Version-Release number of selected component (if applicable): setroubleshoot-3.0.35-1.fc15.x86_64 How reproducible: every time Steps to Reproduce: 1.Wait for SElinux to generate an alert 2.answer yes when asked if you'd like to troubleshoot 3. Actual results: sealert Error widow displays Expected results: GUI appears and allows troubleshooting Additional info: Error window says: raceback (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 This didn't happen before today's yum update replaced report-gtk with libreport-gtk-2.0.3-1.fc15.x86_64, but I haven't encountered any other applications that use it, yet.
On searching this sounds a lot like https://bugzilla.redhat.com/show_bug.cgi?id=715373
Happened on setroubleshoot-3.0.35-1.fc15.i686, too.
*** This bug has been marked as a duplicate of bug 715373 ***