On Tue, Nov 23, 2010 at 10:58 PM, Daniel J Walsh <dwalsh(a)redhat.com> wrote:
>>>>> I have having the following problem with
sealert:
>>>>>
>>>>> # sealert
>>>>> could not attach to desktop process
>>>>> #
>>>>>
>>>>> Any ideas?
>>>>
>>>> sealert -b maybe?
>>>
>>> Thanks, Thomas, but getting the following when running 'sealert -b':
>>>
>>> Nov 23 19:46:33 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.
>>>
>>> Any further ideas?
>>>
>> sealert -s
>
> Thanks, Daniel. With 'sealert -s', I get:
>
> Nov 23 21:50:00 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.
What version of setroubleshoot are you using?
rpm -q setroubleshoot
Are there messages in /var/log/messages concerning setroubleshoot?
# rpm -q setroubleshoot
setroubleshoot-2.2.102-1.fc14.x86_64
#
Yes, there are messages concerning setroubleshoot:
Nov 23 21:49:17 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.
Paul