"Unable to determine the address of the message bus"

wang baisheng bswang at redflag-linux.com
Sun Dec 11 19:22:12 PST 2005


have you export enviroment DBUS_SESSION_BUS_ADDRESS and add user messagebus ?

$ dbus-launch
DBUS_SESSION_BUS_ADDRESS='unix:path=/tmp/session_bus_socket'
DBUS_SESSION_BUS_PID=5899

$export DBUS_SESSION_BUS_ADDRESS='unix:path=/tmp/session_bus_socket'



在 2005年12月10日 星期六 20:34,Tomek Jarzynka 写道:
> Hi,
>
> I've installed KDE 3.5 and wanted to use the new automatic
> media manager, so I installed hal along with DBUS. Unfortunately,
> only the first event is reported (ie inserting a pendrive).
> Further events are not.
>
> I've tried versions 0.23, 0.50 and 0.60 of DBUS with appropriate
> versions of HAL (0.2x(?), 0.5.4, 0.5.5.1) with no luck.
>
> There are no errors in the syslog, both daemons are running,
> but when I try to run dbus-monitor I get:
>
> Failed to open connection to session message bus: Unable to determine the
> address of the message bus.
>
> I don't know if this is the cause of HAL not reporting anything,
> but that's currently the only thing that comes to my mind.
>
> How do I fix this, and/or further debug DBUS and HAL?
>
> This is a gentoo with kernel 2.6.14.3 (didn't work with 2.6.12.1
> either).
>
> Thanks in advance


More information about the dbus mailing list