DBus 1.1.4 and weird message handling

[Ross Burton]

Simon,

On Thu, 2008-01-24 at 13:59 +0000, Simon McVittie wrote:
> On Thu, 24 Jan 2008 at 11:51:16 +0000, Ross Burton wrote:
> > Notice how the client make a LookupExtended call which returned a method
> > reply, and then an error.  Sometimes this happens, sometimes there will
> > just be an error reply.
> 
> Your two replies are coming from bus names :1.0 (success) and :1.1
> (failure), according to the monitor. What processes have those unique names?
> It looks to me as though the method call message got delivered to more
> than one process somehow...

Ah, well spotted.  I just replicated this again:

:1.0 sends back an error signal
:1.1 sends back a correct reply

:1.1 is, as expected, gconfd.  :1.0 is settings-daemon.  This doesn't
use DBus itself, but does link to gconf.

If I kill settings-daemon then I only get the correct replies.  However,
I need settings-daemon, and if I start it again I get the correct
replies still and the monitor shows gconf and settings-daemon still
replying to both, but this time the gconf replies are first.

libgconf requests that the bus start the gconf service, so the question
is does libgconf for some reason receive messages intended for the
server with 1.1 and not 1.0, or does starting a service cause messages
to be routed to it incorrectly?

Ross
-- 
Ross Burton                                 mail: ross at burtonini.com
                                          jabber: ross at burtonini.com
                                     www: http://www.burtonini.com./
 PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF