[MacPorts] #16755: gnucash-2.2.7_2 preferences cannot be accessed/modified: possibly related to orbit2-2.14.16_0, gconf-2.24.0_0 or dbus-1.2.3_0?

[MacPorts]

#16755: gnucash-2.2.7_2 preferences cannot be accessed/modified: possibly related
to orbit2-2.14.16_0, gconf-2.24.0_0 or dbus-1.2.3_0?
----------------------------------------+-----------------------------------
  Reporter:  hypocrite at lawyer.com       |       Owner:  macports-tickets at lists.macosforge.org    
      Type:  defect                     |      Status:  new                                      
  Priority:  Normal                     |   Milestone:  Port Bugs                                
 Component:  ports                      |     Version:  1.6.0                                    
Resolution:                             |    Keywords:  gnucash orbit2 gconf dbus orbit dbus-glib
      Port:  gnucash orbit2 gconf dbus  |  
----------------------------------------+-----------------------------------

Comment(by mp at dpj.sent.com):

 Replying to [comment:16 aoeumacports@…]:
 > [*] 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://www.gnome.org/projects/gconf/ for
 information. (Details -  1: Failed to get connection to session: Failed to
 connect to socket /tmp/dbus-aOhufhZy8k: No such file or directory)

 I'm seeing the exact same thing as you on intel 10.5.5. I think the
 problem has to do with dbus autolaunch. I can get gnucash to work fine by
 starting gnucash with
 {{{
 # dbus-launch gnucash
 }}}

 or by using dbus-launch to set the DBUS_SESSION_ADDRESS and
 DBUS_SESSION_PID environment variables first with (in sh, bash, or zsh)
 {{{
 # eval `dbus-launch --sh-syntax`
 }}}
 Once this is done, then gnucash will start up fine because it has access
 to the session dbus daemon.

 If gnucash (or any program that uses dbus) doesn't have access to the
 session dbus daemon (via the env variables above), it will use the dbus
 autolaunch functionality. This has worked in the past, but doesn't seem to
 work properly with dbus-1.2.4.

 Actually, the dbus documentation suggests that autolaunch is not the best
 idea ("it can be suboptimal or even broken"), so perhaps the dbus port
 should suggest putting the above code in users' login scripts.

-- 
Ticket URL: <http://trac.macports.org/ticket/16755#comment:17>
MacPorts <http://www.macports.org/>
Ports system for Mac OS