GnuGash won't start: The return of gconf/dbus issues.

[A. Osthoff]

David Rowe schrieb:

Hi,

> After the latest MacPorts upgrades, my GnuCash installation won't start:
> 
> GnuCash brings up alert boxes saying: "Cannot find default values - The
> configuration data used to specify default values for GnuCash cannot be
> found in the default system location. . . " and "An error occurred
> whilst loading or saving configuration information for gnucash . . ."
> The terminal log says "Dynamic session lookup supported but failed:
> launchd did not provide a socket path, verify that
> org.freedesktop.dbus-session.plist is loaded!" (this message is repeated
> 6 times).
> 
> Gramps does eventually startup, but the following appears on the
> terminal log: "Dynamic session lookup supported but failed: launchd did
> not provide a socket path, verify that
> org.freedesktop.dbus-session.plist is loaded!
> GConf Error: Failed to contact configuration server; some possible
> causes are that you need to enable TCP/IP networking for ORBit, or you
> have stale NFS locks due to a system crash. See
> http://projects.gnome.org/gconf/ for information. (Details -  1: Failed
> to get connection to session: Not enough memory)".
> 
> Gimp is similar to Gramps - it does start but puts the following message
> in the log: "Dynamic session lookup supported but failed: launchd did
> not provide a socket path, verify that
> org.freedesktop.dbus-session.plist is loaded!
> Not enough memory"
> 
> In my installation, there is a file called
> org.freedesktop.dbus-session.plist in /opt/local/Library/LaunchAgents
> 
> This looks very much like a rerun of the gconf/dbus  incompatibilities
> that caused similar problems towards the end of 2008.
> 
> I tried reverting gconf from the current gconf @2.26.2_0 to the previous
> gconf @2.26.1_0 and the problem was still there. I also tried reverting
> to gconf @2.24.0_2 and that also didn't help (though I see now that the
> workaround for the earlier problems was to revert to gconf @2.22.0_0).
> (By reverting I mean deactivating the new version and then activating
> the old)
> 
> However, reverting dbus from the current dbus @1.2.14_0 to the previous
> dbus @1.2.12_5 seems to make the problem seem to go away (but I have not
> done exhaustive tests).
> 
> So: Is this a problem with my installation or are others hitting the
> same issue?

I already pointed this out on the mailing list on June 6th. ;)
I was able to "re"activate gconf 2.24.0_0 to resolve the issue. (The
current dbus is working fine here).

> If it a general problem, should I raise a ticket?

If I recall the previous discussion correctly a ticket has been already
filed. See
http://www.nabble.com/Updated-Gnucash-doesn%27t-handle-preferences-to19831050.html#a19832473

cheers,
	achim