Thanks Ryan. I must have been looking at some different instructions that Google picked up. The wiki instructions are excellent: very clear and simple.
I can now also confirm that moving from gconf @2.24.0_0 back to gconf @2.22.0_0 solves the problem. I've opened a ticket at http://bugzilla.gnome.org/show_bug.cgi?id=555187 , but left the macports one, just in case the bug is actually unrelated to gconf. Cheers. On 6/10/2008, at 6:02 PM, Ryan Schmidt wrote: > > > On Oct 6, 2008, at 01:11, A. Osthoff wrote: > >>> 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. >> >> Thanks for the pointer and yes, I am able to confirm this. I >> deactivated >> version 2.24.0_0 of gconf and activated 2.22.0_0 and voila, Gnucash >> starts now without a hitch. > > Yes, it is a little complicated to install older versions of ports, > but it is fully documented in the How-To's: > > http://trac.macports.org/wiki/howto/InstallingOlderPort > > > _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
