#45309: gimp2 @2.8.14 on 10.9 - doesn't load plug-ins ---------------------------+---------------------- Reporter: and.damore@… | Owner: devans@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gimp2 | ---------------------------+---------------------- Changes (by devans@…): * status: new => assigned * version: 2.3.1 => * port: gimp2 gimp gimp-app => gimp2 Comment: Thanks for opening this ticket and confirming the problem. It appears there are two separate issues involved here, first the dbus problem and secondly the gimp plugin one. The dbus issue seems to be with the GDBus API provided by the GIO component of glib2. The stock code expects the environment variable DBUS_SESSION_BUS_ADDRESS to be set a session debus address of the form 'unix:path=<path to dbus session socket>'. We have added custom code that attempts to obtain the socket path using the the launchctl command mentioned in the error message if DBUS_SESSION_BUS_ADDRESS is not set. On my 10.9.5 system, manually running the command yields the socket address as follows. {{{ $ launchctl getenv DBUS_LAUNCHD_SESSION_BUS_SOCKET /tmp/launch-vW5khj/unix_domain_listener }}} I can override the GIMP dbus error by setting DBUS_SESSION_BUS_ADDRESS with this value {{{ export DBUS_SESSION_BUS_ADDRESS="unix:path=/tmp/launch- vW5khj/unix_domain_listener" }}} You can get more debugging output from glib2 by setting the additional env variable {{{ export G_DBUS_DEBUG=address }}} This produces the additional output {{{ GDBus-debug:Address: In g_dbus_address_get_for_bus_sync() for bus type 'session' GDBus-debug:Address: env var DBUS_SESSION_BUS_ADDRESS is not set GDBus-debug:Address: env var DBUS_SYSTEM_BUS_ADDRESS is not set GDBus-debug:Address: env var DBUS_STARTER_BUS_TYPE is not set GDBus-debug:Address: launchctl command line: `launchctl getenv DBUS_LAUNCHD_SESSION_BUS_SOCKET' GDBus-debug:Address: Cannot look-up address bus type 'session': Error spawning command line `launchctl getenv DBUS_LAUNCHD_SESSION_BUS_SOCKET': Child process killed by signal 11 }}} This give me an idea of where to look in glib2 to see what's going on. No idea what's going on with the plugin load failures as yet. Will look at it today. -- Ticket URL: <https://trac.macports.org/ticket/45309#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X