[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:23 vinc17@…]:
 > Replying to [comment:22 mp@…]:
 > > I have filed a bug and a patch upstream for dbus at
 https://bugs.freedesktop.org/show_bug.cgi?id=18013
 >
 > This is a different bug: the problem with gconf also appears on 10.4.11,
 where $DISPLAY doesn't have a slash.

 Actually, none of this is a gconf problem. It's all dbus issues, but
 because gconf-2.22 didn't use dbus, gconf-2.23+ exposes these problems.

 The original bug was that X11 support was not compiled into dbus, so dbus
 autolaunch wouldn't work (on all platforms). Once an updated dbus portfile
 was made, both db.evans (comment:12) and pgijnxn02 (comment:15) reported
 success on 10.4ppc.

 Other comments say that the problem didn't go away on 10.5 (comment:16),
 and went away only if dbus-launch was issued manually (comment:20). I am
 guessing that all of these commenters are on 10.5. This is actually a
 different bug to the original "no X11" bug and I will make a new bug
 report so this one can be closed.

 As far as I can see it should all work on 10.4 right now. If you are still
 having problems on 10.4 and you are fully updated, please provide more
 details about the error message that you're seeing.

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