On Wed, May 20, 2009 at 12:16:43PM -0700, Elizabeth Cortell wrote:
> Thanks for your advice. I made marginal progress, but I haven't nailed
> it down yet.
> I added these commands to my .bashrc, sourced it, and tried again:
> if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
> ## if not found, launch a new one
> eval `dbus-launch --sh-syntax --exit-with-session`
> echo "D-Bus per-session daemon address is: $DBUS_SESSION_BUS_ADDRESS"
> And I'd say I got a teeny bit closer, a mere connection refused rather
> than a wholesale Xinit failure:
> ** (process:6106): WARNING **: couldn't connect to dbus session bus:
> Failed to connect to socket /tmp/dbus-5DoJ6SqPqr: Connection refused
Skimming the documentation (man dbus-daemon), it looks like access
to dbus can be restricted to certain programs/user IDs/etc.
You might want to look at the session.conf file in /etc/dbus-1/,
and any files it includes, to find out if the default dbus session
configuration places restrictions on access to the socket.
I guess the set of defaults depends on the distribution.
Both "<policy>" and "<auth>" seem to be relevant keywords to search
the man page and configuration for (though I don't fully understand
how they operate).
Received on 2009-05-20 22:31:55 CEST