gconf2: Fails to notify listeners after SIGHUP

Message-Id: <E1C18Xd-0004qI-00@drno>
Date: Sat, 28 Aug 2004 20:07:09 +0100
From: Crispin Flowerday <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: gconf2: Fails to notify listeners after SIGHUP

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

Message-Id: <email address hidden>
Date: Sun, 29 Aug 2004 00:07:36 +0200
From: Josselin Mouette <email address hidden>
To: Crispin Flowerday <email address hidden>, <email address hidden>
Subject: Re: Bug#268721: gconf2: Fails to notify listeners after SIGHUP

--=-6JNd8dXfWTdv63C6HAJ2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Le samedi 28 ao=C3=BBt 2004 =C3=A0 20:07 +0100, Crispin Flowerday a =C3=A9c=
rit :
> 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.

No. The expected behavior is to have the application see the changes on
startup. If you upgrade from version A to version B while the
application, you want the gconf stuff from version A until you exit the
application and launch it again: then you have version B and you want
the gconf keys of version B.
--=20
 .''`. Josselin Mouette /\./\
: :' : <email address hidden>
`. `' <email address hidden>
  `- Debian GNU/Linux -- The power of freedom

--=-6JNd8dXfWTdv63C6HAJ2
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Ceci est une partie de message
 =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBMQIorSla4ddfhTMRAqbBAKDLyH0NT4wJ6yiakCH9kVpj5iFsGQCgi6Y3
8V3+5leqx1wI1GeEmDshqXE=
=Pw8L
-----END PGP SIGNATURE-----

--=-6JNd8dXfWTdv63C6HAJ2--

Message-Id: <1093731521.2974.2.camel@drno>
Date: Sat, 28 Aug 2004 23:18:41 +0100
From: Crispin Flowerday <email address hidden>
To: <email address hidden>
Subject: Re: Bug#268721: gconf2: Fails to notify listeners after SIGHUP

On Sun, 2004-08-29 at 00:07 +0200, Josselin Mouette wrote:
> Le samedi 28 ao=FBt 2004 =E0 20:07 +0100, Crispin Flowerday a =E9crit :
> > 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.
>=20
> No. The expected behavior is to have the application see the changes on
> startup. If you upgrade from version A to version B while the
> application, you want the gconf stuff from version A until you exit the
> application and launch it again: then you have version B and you want
> the gconf keys of version B.

Huh, I upgrade one gnome package, say Galeon, from A -> B, and _all_
gnome applications using gconf break, how exactly is that expected ?

I understand that, in this case, Galeon might not work quite right, but
I would expect Epiphany/Panel/gnome-settings-daemon to work just fine,
which they don't at the moment.

Crispin

Message-Id: <1093732808.9089.16.camel@seb128>
Date: Sun, 29 Aug 2004 00:40:08 +0200
From: Sebastien Bacher <email address hidden>
To: Crispin Flowerday <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#268721: gconf2: Fails to notify listeners after SIGHUP

severity 268721 serious
forward 268721 http://bugzilla.gnome.org/show_bug.cgi?id=3D148028
thanks

Le samedi 28 ao=FBt 2004 =E0 20:07 +0100, Crispin Flowerday a =E9crit :

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

Hey,

Amazing. Thank you for noticing the SIGHUP relation!

This bug is driving me crazy for some weeks now, it virtual breaks a lot
of apps. The panels changes need a panel kill to be applied, the sticky
applets doesn't work, the epiphany prefs are broken, nautilus doesn't
react to the gconf key changes, ...=20

Neither me or the upstream thought to this before, as you can see on=20
http://bugzilla.gnome.org/show_bug.cgi?id=3D148028

Thank you again for pointing it!

Cheers,

Sebastien Bacher

Message-Id: <E1C1C7D-0001pE-00@seb128>
Date: Sun, 29 Aug 2004 00:56:07 +0200
From: Sebastien Bacher <email address hidden>
To: <email address hidden>
Subject: bug 268721 is forwarded to http://bugzilla.gnome.org/show_bug.cgi?id=148028

# Automatically generated email from bts, devscripts version 2.8.1
forwarded 268721 http://bugzilla.gnome.org/show_bug.cgi?id=148028

Message-ID: <email address hidden>
Date: Sun, 29 Aug 2004 09:05:06 +0200
From: "J.H.M. Dassen (Ray)" <email address hidden>
To: <email address hidden>
Subject: tagging

tags 268721 + sarge sid
thanks

The upstream bugzilla report to which this report is marked "forwarded to"
dates from 2004-07-20 and thus was filed before the Debian packages of 2.6.3
and 2.6.4 were created. The issue is about the gconfd_sighup_reload.diff
patch, and that patch is in the 2.6.3-2 packages currently in sarge as well.
--
"When you are finished spreading joy on Christmas Eve, come and kick back
with me and Erwin for a while. [...] We'll provide the cocoa and cookies,
and we'll even teach you how to play Quake."
 From the Dust Puppy's letter to Santa Claus.

Message-Id: <email address hidden>
Date: Sun, 29 Aug 2004 12:49:48 +0200
From: Josselin Mouette <email address hidden>
To: <email address hidden>
Subject: severity of 268721 is critical

# Automatically generated email from bts, devscripts version 2.8.4
severity 268721 critical

Message-Id: <email address hidden>
Date: Sun, 29 Aug 2004 07:32:10 -0400
From: Josselin Mouette <email address hidden>
To: <email address hidden>
Subject: Bug#268721: fixed in gconf2 2.6.4-2

Source: gconf2
Source-Version: 2.6.4-2

We believe that the bug you reported is fixed in the latest version of
gconf2, which is due to be installed in the Debian FTP archive:

gconf2_2.6.4-2.diff.gz
  to pool/main/g/gconf2/gconf2_2.6.4-2.diff.gz
gconf2_2.6.4-2.dsc
  to pool/main/g/gconf2/gconf2_2.6.4-2.dsc
gconf2_2.6.4-2_i386.deb
  to pool/main/g/gconf2/gconf2_2.6.4-2_i386.deb
libgconf2-4_2.6.4-2_i386.deb
  to pool/main/g/gconf2/libgconf2-4_2.6.4-2_i386.deb
libgconf2-dev_2.6.4-2_i386.deb
  to pool/main/g/gconf2/libgconf2-dev_2.6.4-2_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Josselin Mouette <email address hidden> (supplier of updated gconf2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 29 Aug 2004 12:48:31 +0200
Source: gconf2
Binary: libgconf2-4 gconf2 libgconf2-dev
Architecture: source i386
Version: 2.6.4-2
Distribution: unstable
Urgency: high
Maintainer: Takuo KITAME <email address hidden>
Changed-By: Josselin Mouette <email address hidden>
Description:
 gconf2 - GNOME configuration database system. (daemon and tools, for GNOME
 libgconf2-4 - GNOME configuration database system libraries (for GNOME2)
 libgconf2-dev - GNOME configuration database system development files. (for GNOME
Closes: 268721
Changes:
 gconf2 (2.6.4-2) unstable; urgency=high
 .
   * gconfd_sighup_reload.diff: correctly reopen the connections to the clients
     when reloading the databases (closes: #268721).
Files:
 d76d62733c49d0cfe2bf4c48028de608 1566 libs optional gconf2_2.6.4-2.dsc
 b9cc5ab10ec68b2629b269bdb28f69d3 14606 libs optional gconf2_2.6.4-2.diff.gz
 3892111a9041a91e1c49e85933d5caf7 1089202 admin optional gconf2_2.6.4-2_i386.deb
 c1ce62eee2f94f1602a3243255251acd 64884 libs optional libgconf2-4_2.6.4-2_i386.deb
 3332d264ffbc0dbe1ce3b133f4530695 84330 libdevel optional libgconf2-dev_2.6.4-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBMbpdrSla4ddfhTMRAjmRAKCB2SztU76g4nu3Tt9xZWo2T64OYwCeLLun
1AeXAol+NfxTeYZXepKW8Kg=
=PJbn
-----END PGP SIGNATURE-----

gconf2 (2.7.91.1-0ubuntu1) warty; urgency=low

  * New upstream release:
    - switch off the "subtree-in-a-file" thing again.
  * debian/patches/001_listeners.patch:
    - patch to fix the breakage of dynamic changes all over the desktop
      (was due to a bug in the "reload on sighup" feature) (Warty: #909).

I have gconf2-2.8.1-0ubuntu1 installed and I still have this exact bug. Is it
supposed to be fixed already ?

Strange, this bug has been fixed upstream before 2.8. Why do you think that's
this problem exactly ? You do check this ?

closing as a dup of 1320

This bug has been marked as a duplicate of bug 8077.