Red Hat Bugzilla – Bug 209822
sealert tracebacks when run
Last modified: 2014-03-16 23:03:02 EDT
GTK Accessibility Module initialized
WARNING:root:Could not open log file - using stderr
Introspect error: Message did not receive a reply (timeout by message bus)
Bonobo accessibility support initialized
(setroubleshoot претраживач:3937): libglade-CRITICAL **:
glade_xml_build_interface: assertion `wid != NULL' failed
Traceback (most recent call last):
File "/usr/bin/sealert", line 438, in ?
File "/usr/bin/sealert", line 376, in start_service
File "/usr/bin/sealert", line 350, in main
self.browser = BrowserApplet()
File "/usr/lib/python2.4/site-packages/setroubleshoot/browser.py", line 79, in
File "/usr/lib/python2.4/site-packages/setroubleshoot/browser.py", line 104,
AttributeError: 'NoneType' object has no attribute 'connect_after'
I'm confused by a number of the errors in this report, most of which don't make
sense unless they could be explained by running sealert on a system which
otherwise was having lots of problems. Is this reproducible for you? I can't
I'd have to reinstall. More in a few days.
are you still seeing this?