Bug 592247 - errors and stacktraces logged when starting setroubleshoot
errors and stacktraces logged when starting setroubleshoot
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: setroubleshoot (Show other bugs)
13
All Linux
low Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-14 07:02 EDT by Mads Kiilerich
Modified: 2010-10-04 15:13 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-10-04 15:13:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mads Kiilerich 2010-05-14 07:02:13 EDT
When starting setroubleshoot (from the notification icon) I get this in /var/log/messages.

May 14 12:55:44 localhost setroubleshoot: [dbus.proxies.ERROR] Introspect error on :1.158:/org/fedoraproject/Setroubleshootd: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 14 12:56:09 localhost setroubleshoot: [dbus.ERROR] could not start dbus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 14 12:56:18 localhost setroubleshoot: [rpc.ERROR] exception IndexError: list index out of range#012Traceback (most recent call last):#012  File "/usr/lib/python2.6/site-packages/setroubleshoot/rpc.py", line 942, in handle_client_io#012    self.receiver.feed(data)#012  File "/usr/lib/python2.6/site-packages/setroubleshoot/rpc.py", line 764, in feed#012    self.process()#012  File "/usr/lib/python2.6/site-packages/setroubleshoot/rpc.py", line 756, in process#012    self.dispatchFunc(self.header, self.body)#012  File "/usr/lib/python2.6/site-packages/setroubleshoot/rpc.py", line 974, in default_request_handler#012    self.handle_return(type, rpc_id, body)#012  File "/usr/lib/python2.6/site-packages/setroubleshoot/rpc.py", line 963, in handle_return#012    self.process_async_return(async_rpc)#012  File "/usr/lib/python2.6/site-packages/setroubleshoot/rpc.py", line 811, in process_async_return#012    callback(*async_rpc.return_args)#012  File "/usr/lib/python2.6/site-packages/setroubleshoot/browser.py", line 784, in first_load#012    self.show_current_alert()#012  File "/usr/lib/python2.6/site-packages/setroubleshoot/browser.py", line 598, in show_current_alert#012    alert = self.alert_list[self.current_alert]#012IndexError: list index out of range

The icon showed that there was an alert, but when setroubleshoot started it didn't show any.

setroubleshoot-2.2.83-1.fc13.i686
Comment 1 Daniel Walsh 2010-05-14 10:14:47 EDT
If you rm ~/.setroubleshoot this problem will go away.

Fixed in setroubleshoot-2.2.85-1.fc13.i686

Note You need to log in before you can comment on or make changes to this bug.