-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/23/2010 04:51 PM, Paul Smith wrote:
On Tue, Nov 23, 2010 at 9:42 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.
Paul
What version of setroubleshoot are you using?
rpm -q setroubleshoot
Are there messages in /var/log/messages concerning setroubleshoot?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org/
iEYEARECAAYFAkzsRxAACgkQrlYvE4MpobPYYgCfRjAARqQHbgxE2CeuHWZtTnmN
22cAoLma98EGzsI6BknXhTLZ0fiYEq77
=HpYl
-----END PGP SIGNATURE-----