[MacPorts] #17950: dbus patched with launchd support and version dump

MacPorts noreply at macports.org
Mon Jan 12 02:56:00 PST 2009


#17950: dbus patched with launchd support and version dump
---------------------------------+------------------------------------------
  Reporter:  jonas.baehr@…       |       Owner:  macports-tickets@…                   
      Type:  enhancement         |      Status:  closed                               
  Priority:  Normal              |   Milestone:  Port Enhancements                    
 Component:  ports               |     Version:  1.7.0                                
Resolution:  fixed               |    Keywords:  launchd kde4 x11                     
      Port:  dbus                |  
---------------------------------+------------------------------------------

Comment(by jonas.baehr@…):

 Replying to [comment:13 mta@…]:
 > I get the same problem with gconf-edit, so it's not just a gnucash
 problem.  I enabled logging in both gconf and dbus and in the log I find
 >
 > {{{
 >  GConf-DEBUG: starting (version 2.24.0), pid 631 user 'mta'
 >  Filling in system bus address...
 >    used default system bus
 "unix:path=/opt/local/var/run/dbus/system_bus_socket"
 >  Filling in session bus address...
 >    "launchd:key=session,guid=1753c5538d82685d2d69b9f2496abc69"
 >  Filling in activation bus address...
 >    "launchd:key=session,guid=1753c5538d82685d2d69b9f2496abc69"
 >  Bus activation type was set to "session"
 >  opening shared connection to:
 launchd:key=session,guid=1753c5538d82685d2d69b9f2496abc69
 >  checking for existing connection
 >  creating shared_connections hash table
 >    successfully created shared_connections
 >  GConf-CRITICAL **: Could not connect to session bus: Could not parse
 server address:
 >         Unknown address type (examples of valid types are "tcp" and on
 UNIX "unix")
 > }}}
 >
 > The "opening shared connection" message comes from
 dbus_connection_open_internal.  It then calls
 connection_try_from_address_entry which calls _dbus_transport_open.  This
 function loops over the elements in open_funcs trying to find one that
 recognizes the transport method.  As far as I can tell none of them
 recognize a "launchd" method.  There are three of them (four if
 DBUS_BUILD_TESTS is set) which recognize "tcp", "unix", "autolaunch", and
 maybe "debug-pipe".
 >
 > I must be missing something since this is far too obvious.  What am I
 doing wrong?

 That's really strange. The dbus patch which this bug report is all about
 implements the "launchd" address type. Could you find out where the last
 error comes from (the `GConf-CRITICAL`)? If it forwards a dbus error we
 have to track down this problem, if gconf performs an custom dbus startup
 or address checking, it's a gconf bug (it works for KDE4 and dbus' own
 tools like dbus-monitor).

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


More information about the macports-tickets mailing list