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

[Crispin Flowerday]

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