Description of problem: I had a c++ program crash (a program I wrote myself), and an sealert popped up with the following content: 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 That file seems to belong to setroubleshoot, according to rpm: % rpm -qf /usr/lib64/python2.7/site-packages/setroubleshoot/browser.py setroubleshoot-3.0.37-1.fc15.x86_64 >>> import report >>> print report <module 'report' from '/usr/lib64/python2.7/site-packages/report/__init__.pyc'> 'report/io' contains % l /usr/lib64/python2.7/site-packages/report/io __init__.py __init__.pyc __init__.pyo NewtIO.py NewtIO.pyc NewtIO.pyo TextIO.py TextIO.pyc TextIO.pyo and belongs to the following report package: % rpm -qf /usr/lib64/python2.7/site-packages/report report-0.22-0.fc15.x86_64
This is the same bug as #715373 - "(reportio) Opps, sealert hit an error!"
*** This bug has been marked as a duplicate of bug 715373 ***