Description of problem: sealert crashes on startup : $ sealert Introspect error: Message did not receive a reply (timeout by message bus) (Navigateur setroubleshoot:11512): libglade-CRITICAL **: glade_xml_build_interface: assertion `wid != NULL' failed Traceback (most recent call last): File "/usr/bin/sealert", line 438, in ? start_service() File "/usr/bin/sealert", line 376, in start_service app.main() File "/usr/bin/sealert", line 350, in main self.browser = BrowserApplet() File "/usr/lib/python2.4/site-packages/setroubleshoot/browser.py", line 79, in __init__ self.init_widgets() File "/usr/lib/python2.4/site-packages/setroubleshoot/browser.py", line 104, in init_widgets self.window.connect_after("realize", self.on_realize) AttributeError: 'NoneType' object has no attribute 'connect_after' Version-Release number of selected component (if applicable): setroubleshoot-1.0-1 How reproducible: Always Additional info: setroubleshootd is running: $ pgrep -l setroubleshootd 23772 setroubleshootd DBus is running: $ ps axf | grep dbus 2154 ? Ssl 0:00 dbus-daemon --system 3393 ? Ss 0:00 \_ /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /home/gauret/.xsession 3396 ? Ssl 0:00 /bin/dbus-daemon --fork --print-pid 8 --print-address 6 --session 3397 ? S 0:00 /usr/bin/dbus-launch --exit-with-session /home/gauret/.xsession I'm running KDE.
Given you're in France I'm reasonably sure this is a duplicate of bug #214218, an i18n name was being used incorrectly. You can find a workaround listed there until a new package is posted. If that is not the issue, please feel free to reopen the bug. *** This bug has been marked as a duplicate of 214218 ***