GNOME Bugzilla – Bug 349851
Gconf dialog "Cannot find default values" appears every time
Last modified: 2018-06-29 21:10:48 UTC
From: Chad Smith <smith_cc@yahoo.com> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.12.1 Subject: Cannot find default values Distribution: Unknown Package: GnuCash Severity: minor Version: GNOME2.12.2 2.0.0 Gnome-Distributor: SUSE Synopsis: Cannot find default values Bugzilla-Product: GnuCash Bugzilla-Component: General Bugzilla-Version: 2.0.0 Description: Description of Problem: On execution, program states it cannot find default values and starts wizard even after "update search path" dialog is followed Steps to reproduce the problem: 1. Start gnucash 2. 3. Actual Results: GNUCash prompts that it cannot find default values, and starts wizard to correct the problem Expected Results: After wizard inserts path into .gconf.path, dialog no longer appears How often does this happen? Every time Additional Information: I'm a first time user, but I can't see any effect on the functionality of the program. This is the modification the program made to the .gconf.path file in my home directory: chad@swordtail:~> cat .gconf.path ######## The following lines were added by GnuCash. ######## xml:readwrite:$(HOME)/.gconf xml:readonly:/etc/gconf/gconf.xml.defaults ############## End of lines added by GnuCash. ############## __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------- Bug created by bug-buddy at 2006-08-03 21:34 -------
Thanks for reporting this problem. Can you add the exact distribution version: Suse something? And what is your version of gconf2? Also, I think I've seen the very same problem on my suse9.3 system (gconf2 2.10.0), but I'd need to look into that in the next days.
Ok, I can reproduce this error on my system: The schemas files are installed into $prefix/etc/gconf/schemas/ but *not* anywhere else when I simply run "make install". The ~/.gconf.path file is updated with one readwrite line and this readonly line (where $prefix=/usr): xml:readonly:/usr/etc/gconf/gconf.xml.defaults So obviously the schemas weren't actually being installed into the gconf.xml.defaults directory! Hm... Turns out running "make install" in one of the schemas directories says make[1]: Entering directory `/home/chs/org/gnucash/trunk/src/gnome-utils/schemas' make[1]: Nothing to be done for `install-exec-am'. mkdir -p /usr/etc/gconf/gconf.xml.defaults GCONF_CONFIG_SOURCE=xml::/usr/etc/gconf/gconf.xml.defaults gconftool-2 --makefile-install-rule ./apps_gnucash_history.schemas /bin/sh: gconftool-2: command not found Oooops. But gconftool-2 exists in the rpm "gconf2" which is installed, and it's located in /opt/gnome/bin. Ok, here's the deal: I called "make install" by changing to root, but root's PATH didn't include /opt/gnome/bin. To fix this: Call "su; PATH=/opt/gnome/bin:$PATH make install" instead of directly "make install". We should somehow get make to fail on a missing gconftool-2. It's not sufficient to have ./configure fail, since people will change to root only for make install. And that message should also say how this could be caused. I will submit something to SVN soon.
Can we simply remove the leading '-' characters in src/gnome-utils/schemas/Makefile.am, as below? That way, a missing gcontool-2 will fail here, which is also the first place where it is called during make install. --- Makefile.am (revision 14603) +++ Makefile.am (working copy) @@ -11,8 +11,8 @@ install-data-local: if GCONF_SCHEMAS_INSTALL - -mkdir -p $(DESTDIR)$(GCONF_SCHEMA_CONFIG_SOURCE_DIRONLY) - -GCONF_CONFIG_SOURCE=$(GCONF_SCHEMA_CONFIG_SOURCE) gconftool-2 --makefile-install-rule $(srcdir)/$(schema_DATA) + mkdir -p $(DESTDIR)$(GCONF_SCHEMA_CONFIG_SOURCE_DIRONLY) + GCONF_CONFIG_SOURCE=$(GCONF_SCHEMA_CONFIG_SOURCE) gconftool-2 --makefile-install-rule $(srcdir)/$(schema_DATA) endif
A better solution would be: AC_PATH_PROG(GCONFTOOL, gconftool-2) AC_SUBST(GCONFTOOL) and then in the Makefile we can just use $(GCONFTOOL) That way the fact that the PATH changes during "make install" wont affect this.
A better solution would be: AC_PATH_PROG(GCONFTOOL, gconftool-2) AC_SUBST(GCONFTOOL) and then in the Makefile we can just use $(GCONFTOOL) That way the fact that the PATH changes during "make install" wont affect this. However, yes, we should still probably fail the install via gconftool.
Committed to SVN r14607, awaiting audit/backport.
Committed to branch-2.0, r14624, will be in 2.0.2.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=349851. Please update any external references or bookmarks.