On Tue, Nov 23, 2010 at 9:42 PM, Daniel J Walsh <dwa...@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 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
