[MacPorts] #15081: dbus failure to start after crash

MacPorts noreply at macports.org
Sun Jan 17 00:32:03 PST 2010


#15081: dbus failure to start after crash
-------------------------------------+--------------------------------------
  Reporter:  ld-temp-q6x8@…          |       Owner:  mcalhoun@…           
      Type:  defect                  |      Status:  closed               
  Priority:  Normal                  |   Milestone:                       
 Component:  ports                   |     Version:  1.6.0                
Resolution:  fixed                   |    Keywords:                       
      Port:  dbus                    |  
-------------------------------------+--------------------------------------

Comment(by dports@…):

 I'm running into exactly the same problem with dbus @1.2.16_1:
  {{{
 2010/01/17 03:21:30     org.freedesktop.dbus-system[14253]      Failed to
 start message bus: The pid file "/opt/local/var/run/dbus/pid" exists, if
 the message bus is not running, remove this file
 2010/01/17 03:21:30     com.apple.launchd[1]    (org.freedesktop.dbus-
 system[14253]) Exited with exit code: 1
 2010/01/17 03:21:30     com.apple.launchd[1]    (org.freedesktop.dbus-
 system) Throttling respawn: Will start in 10 seconds
  }}}

 I don't quite follow exactly what changed in r49300 that was supposed to
 fix this.

 It seems to me that (as noted above) the pid file isn't necessary under
 launchd and so it can be disabled by removing the <pidfile> line in
 /opt/local/etc/dbus-1/system.conf. Indeed, removing this line does get the
 system bus running again. (Unfortunately, that's not the only problem I'm
 having with dbus.)

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


More information about the macports-tickets mailing list