dbus-daemon closing connection?

Thiago Macieira thiago at kde.org
Wed Apr 11 21:38:15 PDT 2007


Krishna R wrote:
>Further probing lead to disconnect signal being the cause of
> do_io_error() in dbus-transport-socket.c, it was called because
> do_reading() which reads from the socket and gets bytes_read = 0. That
> means the socket was closed on the other end?

Yes.

>The question i have is why is the dbus-daemon closing the socket? Or is
> it?

It is and it does so because it received an invalid message. If you strace 
the daemon or if you run it in debug mode, it should say why it did that.

>dbus-daemon, A and B are started one after another at boot in the
>foreground. Is there some problem where the session bus is not fully
>initialized? That may not be because atleast one signal from A reaches
> B.

I don't think so.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20070412/4ce07c1d/attachment.pgp


More information about the dbus mailing list