Hide Forgot
I installed Fedora 15 beta from the live cd and then ran a 'yum install gnucash'. I have been using gnucash out of the same home directory in Fedora 13 without issue. When I launch gnucash in Fedora 15 beta, however, I get this message: "Cannot find default values The configuration data used to specify default value for GnuCash cannot be found in the default system locations. Without this data GnuCash will still operate properly but it may require some extra time to setup. Do you wish to setup the configuration data?" I am not sure what this means. Is it a problem with the installation?
If I click to "Skip" the configuration data setup, everything seems to work fine and my old data is there and in tact. But this dialog continues to come up each time I launch it. If I click to set it up, it starts me through this dialog giving me instructions to update my .gconf.path file and such. I quit the dialog without making any changes because it seems like this is an installation problem with gnucash.
I see this on a freshly installed F16, but with a home directory taken over from an older install. Using a newly created user this does not happen.
Affected version: gnucash-2.4.7-4.fc16.x86_64
This has somehow resolved itself for me, I no longer get the error.
Same problem on a fresh installation on F16: "Cannot find default values..." I am unsure how to proceed.
Getting the same on f17 as an ordinary user. For root it loads just fine.
I am having this same issue in Fedora 18 beta.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.