You are not logged in.
Hi,
Since upgrading to Gnome 3.6 I've been getting these errors when upgrading certain Gnome-related packages:
(gconftool-2:12380): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
In most cases the error goes away if I do the following:
$ pacman -Rdd $PACKAGE_GIVING_THE_ERROR
and
$ pacman -S $PACKAGE_GIVING_THE_ERROR
or
$ pacman -S --asdeps $PACKAGE_GIVING_THE_ERROR
depending on whether the package was previously installed explicitly or not.
However, despite doing this some packages still keep giving me the previously mentioned errors:
ekiga gconf-editor gnome-panel gnome-terminal gnome-applets
What does the error mean? Should I be worried? How can I fix this?
Last edited by jtts (2012-11-05 01:49:13)
Offline
I got the same error doing a system update last night. I am using XFCE. Not sure what it means, or the ramifications...
Offline
Similar errors here:
(gconftool-2:4000): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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 was broken.Offline
I managed to find a following solution (at least it worked for me):
1) If you already haven't configured your normal user to be able to 'sudo pacman', do that.
2) As normal user, remove the package that has been giving you the error like this:
$ sudo pacman -Rdd $PACKAGE_GIVING_THE_ERROR
3) Re-install the package (again, as normal user)
$ sudo pacman -S $PACKAGE_GIVING_THE_ERROR
or
$ sudo pacman -S --asdeps $PACKAGE_GIVING_THE_ERROR
depending on whether the package was previously installed explicitly or not.
Re-installing should not give the error message any more.
I have come to the conclusion that the root-user is not able to install the error-giving packages because environmental variable DBUS_SESSION_BUS_ADDRESS has not been set for root user (or maybe it is incorrect).
Anyway, this worked for me at least.
Offline
.
Last edited by silent (2013-08-21 09:04:00)
Offline
You can safely ignore this "error".
To explain this error message a bit: it's an assert raised by the gconf_ping() function used in gconftool-2's shutdown code. Whenever we install schemas from post_install or post_upgrade using gconftool-2, the utility will try to shutdown running gconfd processes through dbus. As root has no dbus session bus and gconf is not running, the gconf_ping() call inside gconftool-2's shutdown code will emit that error.
The last version of gconf has a commit from upstream that fixes the shutdown code, but in return we get this false warning when there's nothing to shut down.
Offline