Bug#252480: gconf2: gconfd exits when Conglomerate starts

[Peter Whysall]

Package: gconf2
Version: 2.6.1-2
Severity: normal

When Conglomerate starts up, it displays an error dialogue:

An error occurred while loading or saving configuration information for XML Editor. Some of your configuration settings may not work properly.

Clicking the Details button reveals the following:

Configuration server couldn't be contacted: CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0
Configuration server couldn't be contacted: CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0

The reason for this is that gconfd has exited.

A brief session in a terminal confirms this:



-- System Information:
Debian Release: testing/unstable
  APT prefers experimental
  APT policy: (1001, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.5
Locale: LANG=C, LC_CTYPE=C

Versions of packages gconf2 depends on:
ii  libatk1.0-0                 1.6.1-2      The ATK accessibility toolkit
ii  libc6                       2.3.2.ds1-13 GNU C Library: Shared libraries an
ii  libgconf2-4                 2.6.1-2      GNOME configuration database syste
ii  libglib2.0-0                2.4.1-2      The GLib library of C routines
ii  libgtk2.0-0                 2.4.1-4      The GTK+ graphical user interface 
ii  liborbit2                   1:2.10.2-1.1 libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0               1.4.0-3      Layout and rendering of internatio
ii  libpopt0                    1.7-4        lib for parsing cmdline parameters
ii  libxml2                     2.6.10-2     GNOME XML library
ii  zlib1g                      1:1.2.1.1-3  compression library - runtime

-- no debconf information