GNOME Bugzilla – Bug 330203
Always "cannot find default gconf values" on startup
Last modified: 2018-06-29 20:56:53 UTC
Please describe the problem: Every time I start gnucash, I get a dialog stating that gnucash "cannot find default values". Then a druid is launched to fix this situation. (I have always accepted all its defaults.) This occurs on every startup. Steps to reproduce: 1. start gnucash 2. 3. Actual results: After the "Cannot find default values" dialog, I get a druid which purports to fix this problem. However, it occurs again on the next startup. Expected results: I expected only to have to go through this druid for one startup. Does this happen every time? Yes. Other information: I am using an opt-style install. The path to gnucash is not in my PATH environment variable. I change to the /opt/gnucash-svn-#####/bin directory and start gnucash by typing "gnucash". I only have one version of gnucash-svn installed at a time. Most recently, I even removed the previous version prior to building the new one (even though the gnucash install location is not on any of my paths and so the current install should not interfere with a new build).
Which distro/OS is this?
I see the same bug. I use SUSE 9.3.
I am using Slackware Linux version 10.2. Kernel version is 2.6.12.
This may be interesting. Here is the contents of my newly created ~/.gconf.path file. (This was created after I deleted the old one as suggested on gnucash-devel to see if this problem was fixed. ######## The following lines were added by Gnucash. ######## xml:readwrite:$(HOME)/.gconf xml:readonly:/opt/gnucash-svn13130/etc/gconf/gconf.xml.defaults ############## End of lines added by Gnucash. ############## ######## The following lines were added by Gnucash. ######## xml:readonly:/opt/gnucash-svn13130/etc/gconf/gconf.xml.defaults ############## End of lines added by Gnucash. ############## Question: could this be related to the opt-style install? Also note that I do "make install DESTDIR=`pwd`/tmp") in order to make a slackware package that I later install. I notice that the referred to file (gconf.xml.defaults) does not exist! Instead the gconf directory contains only a subdirectory called schemas. It looks as though the druid is adding to the end of this file each time gnucash is run. A third run confirms this.
The problem is that you're installing from a package instead of installing directly from source. The gconf default key values aren't being written to your temporary destination directory and thus aren't included in the package. Other applications that use gconf (c.f. evolution, evince, etc) only include the schemas in the package and then install the default key values as part of the rpm post-install script. I'll have to go look at the build systems for one of these applications and see if I can figure out how to fix gnucash so that keys are installed correctly for both developers and packagers. The duplicate lines in .gconf.path are a problem that needs to be fixed.
Also note that on http://www.gnome.org/projects/gconf/ , section "Application developer information", the GConf documentation explicitly states that with package building, the packagers are expected to "disable schema installation during the "make install" phase" and "then in the post-install script, run something" else. In other words, it's not directly clear whether this problem should be fixed in gnucash or is rather a conceptual problem of gconf.
Well, as said before, I get the same error. But I build from SVN: ./autogen.sh ./configure --prefix=/opt/gnucash/test_install/cvs_head --with-g-wrap-prefix=/opt/gnucash/g-wrap-latest --build=i686-pc-linux-gnu make su make install I even deleted the whole tree under /opt/gnucash/test_install/cvs_head and built from a fresh SVN checkout. I still get the druid every time I start gnucash. This happens on a SUSE 9.3 system. I just built on a SUSE 10.0 system and there it works (i.e. the druid shows up only the first time I start GnuCash).
Is this still a problem on 9.3? Can the bug report be closed?
Comments #5 & #6 explained it for me. I modified my packaging scripts so that the values are written to gconfd during the install of the package. I don't know if comment #7 is fixed.
comment #7 is still valid. I think the problem is that make install does not install anything into /opt/gnucash/test_install/cvs_head/etc/gconf/gconf.xml.defaults/
I downloaded and installed SuSe 9.3 into a virtual machine, then compiled and installed gnucash. I do not see this behavior. Gnucash presented the "cannot find default values" dialog once, and has not presented it a second time. I can only conclude that the problem is specific to your suse 9.3 system and not a general problem with gnucash or suse 9.3, so I'm closing this bug.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=330203. Please update any external references or bookmarks.