#26712: dbus @1.2.24_1: Start error - Socket error ----------------------------+------------------------ Reporter: fokkovisser@… | Owner: mcalhoun@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Resolution: worksforme | Keywords: Port: dbus | ----------------------------+------------------------ Comment (by devans@…): Replying to [comment:9 ryan.young.baylor@…]:
I also get the same error, newest version of dbus, Mac OS X 10.10.4 .. no clue what to do about it. Ran the code suggested by {{{port notes dbus}}}. But no cigar.
{{{sudo dbus-launch bash}}}
{{{Failed to start message bus: launchd's environment variable DBUS_LAUNCHD_SESSION_BUS_SOCKET is empty, but should contain a socket path.}}}
{{{EOF in dbus-launch reading address from bus daemon}}}
On Mac OS X, dbus-launch is not used to start a session dbus instance, say at user login time, as it typically is on Linux implementations. Rather OS X's launchd facility is used instead as outlined in the notes from the dbus port. So when you execute the command {{{ launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist }}} the session dbus instance is immediately started (if it doesn't already exist) and will similarly be started each time you login thereafter. You only have to do this once. Having executed this command you can verify that the session bus is running using {{{ $ ps ax | grep dbus 21714 ?? S 0:00.37 /opt/local/bin/dbus-daemon --nofork --session }}} Similarly you can verify that DBUS_LAUNCHD_SESSION_BUS_SOCKET env var is set using something like this {{{ $ env | grep DBUS DBUS_LAUNCHD_SESSION_BUS_SOCKET=/private/tmp/com.apple.launchd.rvlgFyFZuj/unix_domain_listener }}} If you want to stop the session bus, just use the same command with 'unload' instead of 'load'. {{{ launchctl unload -w /Library/LaunchAgents/org.freedesktop.dbus- session.plist }}} I should note that using sudo with dbus-launch is why your got the DBUS_LAUNCHD_SESSION_BUS_SOCKET error. The session bus is running in your user session, not that of the privileged user. Since this is an old ticket and has been closed, if you need more help with this issue please inquire on the macports-users email list. Thanks. -- Ticket URL: <https://trac.macports.org/ticket/26712#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X