Ubuntu – glib.GError: No D-BUS daemon running

dbus

When trying to run meld on Ubuntu Desktop 13.04, I get the following error:

$ meld

(meld:1509): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-EQeHnPP7h5: Connection refused
Traceback (most recent call last):
   ...
glib.GError: No D-BUS daemon running

I am running as a non-root user, with a X11 forwarding through PuTTY/SSH to Xming.

Best Answer

This bug pointed me to two ways to fix it, of which I used:

eval $(dbus-launch --sh-syntax)

export DBUS_SESSION_BUS_ADDRESS
export DBUS_SESSION_BUS_PID

Related Solutions

Ubuntu – My ubuntuone is broken, what is the problem

Are the only lines in ~/.cache/ubuntuone/log/syncdaemon.log look like

$date - ubuntuone.SyncDaemon.VM.MD - DEBUG - metadata version: 6
$date - ubuntuone.SyncDaemon.fsm - INFO - loading updated metadata

If yes, then this may be the result of the following:

A lot of metadata files/folders in ~/.local/share/syncdaemon/fsm leading to syncdaemon startup taking more than 2 minutes - bug LP:683116.

You may want to cleanup syncdaemon directories by running the following command while syncdaemon is not running. The first one will give you the info about how many directories can be cleaned up:

find ~/.local/share/ubuntuone/syncdaemon -depth -type d -empty | wc -l

And this one will delete empty directories:

find ~/.local/share/ubuntuone/syncdaemon -depth -type d -empty -delete

After that running the first command should return 0 as the amount of directories. Subsequent starts should be faster.

GConf Error: No D-BUS Daemon Running – How to Reinstall or Fix

SirCharlo's answer worked for me. Same problem on ubuntu 12.04 (precise pangolin). Yeah, I use su (root) also. Shame, shame. Same problem starting emacs too.

The problem seems to be that DBUS_SESSION_BUS_ADDRESS retains its value when you su instead of picking up the value in /root/.dbus/session-bus/

from man dbus-launch:

   ...
   The second common reason for autolaunch is an su to another  user,  and
   display  of  X  applications  running as the second user on the display
   belonging to the first user. Perhaps the ideal fix in this  case  would
   be  to allow the second user to connect to the session bus of the first
   user, just as they can connect to the first user's display.  However, a
   mechanism for that has not been coded.
   ...

Use sudo, suedit, gksu.

Or if you MUST use su, then try adding this to your /root/.bashrc:

sessionfile=`find "${HOME}/.dbus/session-bus/" -maxdepth 1 -type f`
if [ -f "$sessionfile" ] ; then
    if grep -q "^DBUS_SESSION_BUS_ADDRESS=" "${sessionfile}" ; then
        export `grep "^DBUS_SESSION_BUS_ADDRESS=" "${sessionfile}"`
    else
        echo "DBUS_SESSION_BUS_ADDRESS not found in ${sessionfile}"
    fi
else
    echo "no session address file found in ${HOME}/.dbus/session-bus"
fi

Best Answer

Related Solutions

Ubuntu – My ubuntuone is broken, what is the problem

GConf Error: No D-BUS Daemon Running – How to Reinstall or Fix

Related Question