After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 83015 - new keys in schema do not get applied to old instances
new keys in schema do not get applied to old instances
Status: RESOLVED DUPLICATE of bug 107692
Product: GConf
Classification: Deprecated
Component: gconf
CVS HEAD
Other other
: Normal major
: ---
Assigned To: GConf Maintainers
Luis Villa
Depends on:
Blocks:
 
 
Reported: 2002-05-25 20:45 UTC by Thomas Vander Stichele
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description Thomas Vander Stichele 2002-05-25 20:45:49 UTC 
When a package is upgraded and there are new keys in the schema, then these
new keys do not get automatically added as defaults to old instances of
this package in GConf.

Example in case :
- I upgraded from garnome 0.9.5 to 0.10.1
- gnome-panel in 0.10.1 has minimum_size and maximum_size as new keys in
  the tasklist.schema
- my already configured panel with tasklist ended up not being shown since
  the preferences show "0" for both minimum and maximum size

I don't know if it's possible or easy doable, but it would be very nice if,
on installing schemas, it would check for new keys and apply these new
defaults to all the current instances already registered in GConf.
Comment 1 Luis Villa 2002-05-29 18:31:04 UTC 
Sounds like something that will be necessary in Real Environments,
Havoc, so I'm marking major- please tell me if I'm on crack :)
Comment 2 Havoc Pennington 2003-03-06 03:56:26 UTC 
Should get autofixed if we make notification based on file changes 
rather than relying on stuff going through the daemon.

*** This bug has been marked as a duplicate of 107692 ***