How does a home user fix a broken DBUS ?
hp at redhat.com
Tue Jan 9 07:47:30 PST 2007
Rod Butcher wrote:
> dbus_message_new_error (reply_to=0x5b2d00,
> error_name=0x2b6f0825c6e8 "org.freedesktop.DBus.Error.NoReply",
> error_message=0x2b6f0825e250 "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 w"...) at dbus-message.c:1200
> The messagebus is running.
> /var/run/dbus/system_bus_socket exists with permissions rw for all.
> I have seen quite a few such messages on bulletin boards with never an
Well, except for the rather long one in the error message itself ;-)
> Can you guys suggest how I debug why no reply is coming from the
> messagebus ?
I would suggest either strace (perhaps on the daemon) or starting the
daemon with verbose logging enabled. It would take me a while to put
together a step-by-step on how to get verbose logging, I'm not sure what
the tricks are offhand.
> To me this is nasty - nothing concrete to investigate
> further, just a dead end. How do I debug why the messagebus didn't reply
> ? Permissions, userid, wrong name, wrong socket ? How to debug something
> that won't reply ?
You have to debug it on the other end, the daemon instead of the app
talking to it.
More information about the dbus