Bug#268721: gconf2: Fails to notify listeners after SIGHUP

[Crispin Flowerday]

Package: gconf2
Version: 2.6.4-1
Severity: important

If you give gconfd-2 a SIGHUP, as I believe happens when a gnome
package is upgraded, it seems to forget about applications listening
for changes. This is confusing for users, as they change things, and
the application doesn't change as expected.

To reproduce:

1) killall -USR1 gconfd-2 (to get verbose logging in the syslog)
2) Run gnome-theme-manager, and check that it changes theme when
   you select a new theme
3) killall -HUP gconfd-2
4) Wait till you see " Reloading all databases" in the syslog (you may need
to change a few keys to get this to occur)
5) Now change the theme again.

Notice that the last time the theme is changed, gconf is told of the
keys being changed, but doesn't notify applications listening.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8

Versions of packages gconf2 depends on:
ii  libatk1.0-0                 1.6.1-3      The ATK accessibility toolkit
ii  libc6                       2.3.2.ds1-16 GNU C Library: Shared libraries an
ii  libgconf2-4                 2.6.4-1      GNOME configuration database syste
ii  libglib2.0-0                2.4.6-2      The GLib library of C routines
ii  libgtk2.0-0                 2.4.9-1      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.1-2      Layout and rendering of internatio
ii  libpopt0                    1.7-4        lib for parsing cmdline parameters
ii  libxml2                     2.6.11-3     GNOME XML library
ii  zlib1g                      1:1.2.1.1-7  compression library - runtime

-- no debconf information