Re: Sealert does not pop up as a desktop window

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Nov 24, 2010 at 1:12 PM, Daniel J Walsh <dwalsh@xxxxxxxxxx> 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?

Paul
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux