GNOME Bugzilla – Bug 50160
GConf gets confused about notification when using non-default contexts
Last modified: 2005-11-20 01:01:32 UTC
Package: gconf Version: CVS If you change a value without using the default context, but your non-default source is part of the default source stack, GConf won't notice. Havoc ------- Bug moved to this database by martin@bugzilla.gnome.org 2000-12-16 16:25 ------- This bug previously known as bug 3534 at http://bugs.gnome.org/ http://bugs.gnome.org/show_bug.cgi?id=3534 Originally filed under the gconf product and general component. The original owner of this bug does not have an account here. Reassigning to the person who moved it here, martin@bugzilla.gnome.org. Previous owner is unknown. Bug assigned to new owner, setting status to "NEW". Previous status was "UNCONFIRMED".
Re-assigning, since martin isn't involved ATM. hp- this is a fairly old bug; is it still relevant?
Argh. and moving out of unconfirmed.
Yes, this bug still exists, but I'm ignoring it for gnome 2. It doesn't matter too much in practice.
*** This bug has been marked as a duplicate of 107692 ***