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 58704 - the FIXME on xml-entry.c:370 needs uregent fixing
the FIXME on xml-entry.c:370 needs uregent fixing
Status: RESOLVED FIXED
Product: GConf
Classification: Deprecated
Component: XML backend
CVS gconf-1-0
Other Linux
: Normal major
: ---
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-08-07 20:20 UTC by Yanko Kaneti
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Fix based on gconf-1-0 branch (1.27 KB, patch)
2001-08-12 10:34 UTC, Marco Pesenti Gritti 		none Details | Review

Description Yanko Kaneti 2001-08-07 20:20:22 UTC 
having gconfd flooding the syslog, even if working correctly is not good

its very obvious for all galeon users, as it happens on first access to 
every conf dir
Comment 1 Marco Pesenti Gritti 2001-08-12 10:34:43 UTC 
Created attachment 876 [details] [review]
Fix based on gconf-1-0 branch
Comment 2 Marco Pesenti Gritti 2001-08-12 10:41:51 UTC 
The patch assumes that when a schema attribute exists there is no
default value, so it doesnt log the error. I verified this is true for
the schema installation and for .gconf but I really dont know if it's
the right thing.
If my assumption is wrong please ignore the patch.