Opened 12 years ago

Closed 9 years ago

#32945 closed defect (worksforme)

dbus needs unloading and reloading the .plist items in order for applications to connect to it

Reported by: vlsd (Vlad) Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: vlsd (Vlad)
Port: dbus

Description

On Snow Leopard, I have this recurring problem where applications that want to connect to dbus will randomly give errors that dbus is not running, even though it is. For example, when I start Inkscape, I get

Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Failed to get connection
** (inkscape:5585): CRITICAL **: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed

** (inkscape:5585): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

** (inkscape:5585): CRITICAL **: dbus_g_connection_register_g_object: assertion `connection != NULL' failed

and similar output from gimp and other applications. However, when I try to load the .plist object, I get

# launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist
org.freedesktop.dbus-session: Already loaded

The way around this is to first call launchctl and tell it to unload the item then reload it. After that Inkscape and gimp start with no errors for a couple of days, until the problem reoccurs.

Change History (3)

comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to mcalhoun@…

comment:2 Changed 12 years ago by vlsd (Vlad)

Cc: vloodo@… added

Cc Me!

comment:3 Changed 9 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Resolution: worksforme
Status: newclosed

dbus has undergone numerous revisions since this ticket was opened (apologies for never acknowledging).
I have never encountered this problem.
Closing now with the hope that the problem has been solved in the interim.
We can reassess if there is still a problem.

Note: See TracTickets for help on using tickets.