Sealert does not pop up as a desktop window

Paul Smith phhs80 at gmail.com
Tue Nov 30 17:00:24 UTC 2010


On Tue, Nov 30, 2010 at 2:03 PM, Daniel J Walsh <dwalsh at 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
>>> What about
>>>
>>> # ausearch -m avc -ts recent
>>
>> Thanks, Daniel. Sorry for my delay, but I was a few days away from computers.
>>
>> Answering now your question:
>>
>> # sealert -b
>> # ausearch -m avc -ts recent
>> <no matches>
>> #
>>
>> And still getting:
>>
>> Nov 29 22:19:22 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.
>>
>> Should I use Bugzilla for this?
>
> Yes although I am not sure if this is a setroubleshoot or dbus problem.

Thanks, Daniel. It is done against dbus:

https://bugzilla.redhat.com/show_bug.cgi?id=658544

Paul


More information about the users mailing list