Hi, I opened up a ticket for this yesterday, but good to know other people have got the same problem: http://trac.macports.org/ticket/16755
You might notice the last post says: "Here the problem disappears after deactivating gconf @2.24.0_0 and reactivating gconf @2.22.0_0. So, I suppose the bug is in gconf @2.24.0_0." Unfortunately, I've gone and deleted my old installation already, and it appears it's a little complicated to activate old versions of ports, unless they're already installed. If you can confirm that the bug is in gconf @2.24.0_0, I'm sure that'd be useful. I was going to post to http://bugzilla.gnome.org/ as well, as that's where the gconf page says to post, however I just saw this: http://bugzilla.gnome.org/show_bug.cgi?id=425060 I'm not sure if this is related? Some of the posts are over a year ago. I'm a bit too terminal-phobic to attempt the workaround, but if it works for anyone, please let me know. Cheers. On 6/10/2008, at 10:52 AM, David Rowe wrote: > > I have been using Gnucash 2.2.x for a while now with few problems. > > However after a recent set of updates, the new 2.2.7 is not working > properly: > > On starting, Gnucash opens a message box saying: > "An error occurred while loading or saving configuration information > for > gnucash. Some of your configuration settings may not work properly" > This > box won't go away while Gnucash is running. > > It also opens another message box saying: > "Cannot find default values. > The configuration data used to specify default values for Gnucash > cannot > be found in the default system locations. . . . Do you wish to set up > the configuration data?" > > You can the follow a dialogue that is trying to set up configuration > data - but it doesn't work and I will get the same messages next > time I > run Gnucash. > > Gnucash does eventually run but you can't change any of the > preferences. > > I suspect that the problem is not in Gnucash itself but in the > dependencies that were also updated about a week ago. I tried > deactivating Gnucash 2.2.7 and reactivating 2.2.5 - which used to work > OK. However 2.2.5 now shows exactly the same problems. > > I note the recent discussions about gnucash, aqbanking and gwenhywfar, > so for the record my current configuration for these is: > > "bash-3.2# port installed aqbanking aqbanking3 gwenhywfar gwenhywfar3 > gnucash > The following ports are currently installed: > aqbanking @2.3.3_0 > aqbanking @3.7.2_0 (active) > aqbanking3 @3.7.1_0 > gwenhywfar @2.5.3_0 > gwenhywfar @3.4.1_0 (active) > gwenhywfar3 @3.4.1_0 > gnucash @2.2.5_0 > gnucash @2.2.5_1 > gnucash @2.2.7_0 > gnucash @2.2.7_1 > gnucash @2.2.7_2 (active) > " > > Does anyone have any suggestions on how to fix this problem? > > David Rowe > > > > > > > _______________________________________________ > macports-users mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
