Bug#711597: gconf2: gconftool-2 in postinst cannot connect to D-BUS

[Kitty Box]

Hi,

I've recently encountered this error as described by the bug reporter. This
error needs to fixed asap in my opinion. Many of my programs seem to run
gconf2 postinst when the gonf2 fails they get marked as broken by aptitude.
See below:



$ sudo aptitude reinstall pidgin
The following packages will be REINSTALLED:
  pidgin
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 12
not upgraded.
Need to get 0 B/599 kB of archives. After unpacking 0 B will be used.
(Reading database ... 176671 files and directories currently installed.)
Preparing to replace pidgin 2.10.7-2+b1 (using
.../pidgin_2.10.7-2+b1_amd64.deb) ...
Unpacking replacement pidgin ...
Processing triggers for gconf2 ...

(gconftool-2:5047): GConf-WARNING **: Client failed to connect to the D-BUS
daemon:
/usr/bin/dbus-launch terminated abnormally with the following error: No
protocol specified
Autolaunch error: X11 initialization failed.

Processing triggers for man-db ...
Processing triggers for menu ...
Processing triggers for desktop-file-utils ...
Processing triggers for mime-support ...
Setting up pidgin (2.10.7-2+b1) ...
Processing triggers for menu ...

aptitude search ~b
iB  pidgin                                              - graphical
multi-protocol instant messaging client for X

My current workaround is to install the packages from stable using:

sudo aptitude install gconf2=3.2.5-1+build1 gconf-service=3.2.5-1+build1
libgconf-2-4=3.2.5-1+build1 gconf2-common=3.2.5-1+build1
libgconf2-4=3.2.5-1+build1 gconf-defaults-service=3.2.5-1+build1

Kitty
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20131219/b96efa0d/attachment.html>