Sealert does not pop up as a desktop window

[Paul Smith]

Dear All,

I have having the following problem with sealert:

# sealert
could not attach to desktop process
#

Any ideas?

Thanks in advance,

Paul

[Paul Smith]

On Tue, Nov 30, 2010 at 2:03 PM, Daniel J Walsh <dwalsh(a)redhat.com&gt; 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

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/29/2010 05:19 PM, Paul Smith wrote:
>  On Wed, Nov 24, 2010 at 1:12 PM, Daniel J Walsh
> <dwalsh(a)redhat.com&gt; 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 
Yes although I am not sure if this is a setroubleshoot or dbus problem.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkz1BEwACgkQrlYvE4MpobPHUQCeJoaS+A1DNnrg0dd3BFuYhnUB
> GVAAoMTImlU1OexOlKrLa0kWAgyLrQX7
> =KQ7N
> -----END PGP SIGNATURE-----

[Paul Smith]

On Wed, Nov 24, 2010 at 1:12 PM, Daniel J Walsh <dwalsh(a)redhat.com&gt; 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

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/23/2010 06:07 PM, Paul Smith wrote:
>  On Tue, Nov 23, 2010 at 10:58 PM, Daniel J Walsh
> <dwalsh(a)redhat.com&gt; 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

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkztDz8ACgkQrlYvE4MpobPBDACfQ1aDD4RUHu2wdYMNoqUTnUrE
> xEQAn094QaUcEE3SVPJdyVtQjctvJI1Z
> =ky4A
> -----END PGP SIGNATURE-----

[Paul Smith]

On Tue, Nov 23, 2010 at 10:58 PM, Daniel J Walsh <dwalsh(a)redhat.com&gt; 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

[Daniel J Walsh]

-----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&gt; 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-----

[Paul Smith]

On Tue, Nov 23, 2010 at 9:42 PM, Daniel J Walsh <dwalsh(a)redhat.com&gt; 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

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/23/2010 02:48 PM, Paul Smith wrote:
>  On Tue, Nov 23, 2010 at 7:22 PM, Thomas Cameron
>  <thomas.cameron(a)camerontech.com&gt; 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?
>  
>  Paul 
sealert -s


> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkzsNTkACgkQrlYvE4MpobO6TgCgyae7KIU3boFCVxfF3GIUXE8P
> Ld8AoJnUUA+JZqHPTgkgftePzpqnTNJ3
> =EBZg
> -----END PGP SIGNATURE-----

[Paul Smith]

On Tue, Nov 23, 2010 at 7:22 PM, Thomas Cameron
<thomas.cameron(a)camerontech.com&gt; 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?

Paul

[thomas cameron]

On 11/23/2010 07:07 AM, Paul Smith wrote:
>  Dear All,
>
>  I have having the following problem with sealert:
>
>  # sealert
>  could not attach to desktop process
>  #
>
>  Any ideas?
>
>  Thanks in advance,
>
>  Paul 
sealert -b maybe?