As logged in syslog: Sep 12 09:44:24 setroubleshoot: [dbus.proxies.ERROR] Introspect error on :1.106:/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. Sep 12 09:46:46 setroubleshoot: [rpc.ERROR] [delete_signature] 1001 signature not found Sep 12 09:46:46 setroubleshoot: [rpc.ERROR] [delete_signature] 1001 signature not found Sep 12 09:46:46 setroubleshoot: [rpc.ERROR] [delete_signature] 1001 signature not found
setroubleshoot-2.2.28-1.fc12.x86_64
Did you do anything to trigger this? IE Did you try the fixit button?
no idea, don't even know what the fixit button is
Does setroubleshoot seem to be working for you?
It works right now, but I admit I had to restart it manually a few times this week
There should be no restarting, are you talking about seapplet? The only constantly running components in Rawhide should be sedispatch which listens to audit for avc messages and seapplet which listens for setroubleshoot messages. If an AVC arrives, audit sends a message to seapplet which sends a dbus message to setroubleshoot, dbus will start setroubleshoot if it is not running, setroubleshoot sends a dbus message to seapplet which puts up the star. If the user clicks on the star it will launch sealert which talks to setroubleshoot, (Starting it if it is not running). setroubleshoot dies 10 seconds after the sealert browser exits and any avc message arrives.
sealert yes
BTW I hit this a few hours ago Sep 14 19:58:21 setroubleshoot: [dbus.proxies.ERROR] Introspect error on :1.106:/org/fedoraproject/Setroubleshootd: dbus.exceptions.DBusException: org.freedeskt op.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 repl y, the reply timeout expired, or the network connection was broken. Sep 14 19:58:46 setroubleshoot: [dbus.ERROR] could not start dbus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the rem ote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
It seems to be working fine now.