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 117712 - Misuse of enum causes recursive unset to fail on schemas
Misuse of enum causes recursive unset to fail on schemas
Status: RESOLVED FIXED
Product: GConf
Classification: Deprecated
Component: gconf
CVS HEAD
Other Linux
: High normal
: ---
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-07-17 20:07 UTC by Greg Hudson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to assign non-zero value to GCONF_UNSET_INCLUDING_SCHEMA_NAMES (469 bytes, patch)
2003-07-17 20:08 UTC, Greg Hudson
none Details | Review

Description Greg Hudson 2003-07-17 20:07:47 UTC
GCONF_UNSET_INCLUDING_SCHEMA_NAMES (a constant which lives in
gconf-sources.h in the released version, and in gconf-value.h in the CVS
head) is defined using an enum, but with no explicit assignment, it gets
the value 0.  So it has no effect, and recursive unsets always fail to
remove schemas.

(As a consequence, gconftool-2 --recursive-unset /apps/panel results in a
broken panel configuration; the default panel profile directory still
exists, so the default schema doesn't get re-associated.)

I will attach a patch against the CVS head; obviously, the same change to
gconf-sources.h in the release version will work there.
Comment 1 Greg Hudson 2003-07-17 20:08:33 UTC
Created attachment 18392 [details] [review]
Patch to assign non-zero value to GCONF_UNSET_INCLUDING_SCHEMA_NAMES
Comment 2 Havoc Pennington 2003-07-17 20:24:16 UTC
Thanks, brown paper bag bug.

I'm applying to cvs now.