DBUS connection refused
rohit.chaudhri at gmail.com
Sun Mar 12 09:56:30 PST 2006
Thanks for your responses. My Ubuntu desktop does have dbus installed,
the version is 0.36 while I am running tests on dbus version 0.60. If
dbus-launch always starts up the system bus (0.36 in my case) then
the version 0.60 test code will try to communicate with the system
bus, which are incompatible.
I'll upgrade dbus installed on my desktop.
On 3/12/06, John (J5) Palmieri <johnp at redhat.com> wrote:
> You can't run the tests directly per say. They are unit tests and are
> designed to be run from within the tarball using 'make check'. They are
> linked to the libraries in the tarball while running dbus-launch would
> start up the bus installed on the system. Between 0.3x and 0.6x we
> changed the ABI of how sockets are added to the system. In the old
> version they were fixed length with the unused portion of the socket
> name being padded by \0 bytes. The newer ABI specifies that the socket
> name should be truncated. This means that a newer library trying to
> talk to an older daemon will not be able to connect to each other
> because they view socket names very differently.
> On Sat, 2006-03-11 at 17:48 -0600, Rohit Chaudhri wrote:
> > Hello,
> > I have recently built DBUS version 0.60 on my Ubuntu desktop. I want
> > to use DBUS as the IPC mechanism for some apps I'll implement so am
> > trying to understand how it works.
> > When trying to run some of the tests in the tests/ directory I always
> > get an error message saying that the connection was refused. I'm
> > pasting below the details of the error message, would appreciate any
> > help regarding this.
> > I first launch a session bus using bin/dbus-launch, this prints the following:
> > DBUS_SESSION_BUS_ADDRESS='unix:abstract=/tmp/dbus-eQRpBp1phI,guid=555c13447a71593210a04946430c2f00'
> > DBUS_SESSION_BUS_PID=22724
> > I set an environment variable called DBUS_SESSION_BUS_ADDRESS with the
> > value as printed above.
> > After this I try running the tests in the tests directory and get the
> > following error:
> > test-service
> > *** Failed to open connection to activating message bus: Failed to
> > connect to socket /tmp/dbus-eQRpBp1phI: Connection refused
> > chaudhri at bhramanda:~/workspace/dbus-0.60/test$ test-names
> > *** Failed to open connection to system bus: Failed to connect to
> > socket /tmp/dbus-eQRpBp1phI: Connection refused
> > test-names is looking for the system bus it seems, I have the system
> > bus running on my machine, how can I configure test-names to use the
> > system bus correctly? Maybe the other tests also need to use the
> > system bus, so if I can get one test to work then maybe others will
> > work too I think.
> > Thanks.
> > _______________________________________________
> > dbus mailing list
> > dbus at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/dbus
> John (J5) Palmieri <johnp at redhat.com>
More information about the dbus