dbus-session error on some apps that used to work

Questions about Wine on macOS.
Locked
jimfisheye
Newbie
Newbie
Posts: 2
Joined: Sat Oct 20, 2012 9:44 pm

dbus-session error on some apps that used to work

Post by jimfisheye »

I'm getting this error:
Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!

I went thru this a while back. Installed winetricks, followed the instructions and all was well.

The only thing I did in the interim was update OSX 10.6.7 to 10.6.8. And now I get this error again on 2 apps. One (Surcode MLP) used to run.

What did I break?
jimfisheye
Newbie
Newbie
Posts: 2
Joined: Sat Oct 20, 2012 9:44 pm

Re: dbus-session error on some apps that used to work

Post by jimfisheye »

Can anyone point me in any direction here to troubleshoot this? I'm hoping to avoid starting over installing wine (and possible reverting back to an older OSX). I'm not sure what to try since I originally did the workaround to run this app and it originally worked.

I just tried to install this demo for Tmpeg Authoring Works 5 and got errors. I don't know if this is related or just a flawed demo. Every other older windows app I have still runs except for Surcode MLP.
ischou
Level 4
Level 4
Posts: 109
Joined: Sun Nov 28, 2010 7:22 pm

Re: dbus-session error on some apps that used to work

Post by ischou »

It has something to do with your dbus installation. Make sure Fink or MacPorts built and installed dbus.

Make sure dbus was started by launchd and isn't crashing every 60 seconds by opening your Console.app and making sure there aren't an endless list of error messages that look something like:

Feb 11 20:36:40 yourhost launchd: org.freedesktop.dbus-session: respawning too quickly! throttling
Feb 11 20:36:40 yourhost launchd: org.freedesktop.dbus-session: 9 more failures without living at least 60 seconds will cause job removal
Feb 11 20:36:40 yourhost launchd: org.freedesktop.dbus-session: will restart in 10 seconds

Look at this post:

https://trac.macports.org/ticket/19804

for an example of how to manually load dbus into launchd if MacPorts failed to do so correctly.

Finally, check that your environment has a environment variable to tell dbus which socket to use:

DBUS_SESSION_BUS_ADDRESS=launchd:env=DBUS_FINK_SESSION_BUS_SOCKET

or whatever launchctl getenv spits out for dbus socket
Locked