gimp2 2.6.4_1 gimp-remote is no longer built automatically

[edheil@…]

gimp-remote, which is needed by gimp-app, is no longer built automatically in gimp 2.6.

You need to add:

--enable-gimp-remote

to configure.args to get it back.

[devans@…]

The gimp-remote program is now deprecated by the developers in favor of an equivalent functionality that is now built into the gimp program which uses dbus. On startup, dbus registers an Open method with the dbus session bus. If a second instance of gimp is invoked with URL/file arguments, it passes the request to the existing instance using the Open method via dbus.

So with dbus support enabled you should be able to use the command 'gimp <url>' instead of gimp-remote with the same functionality.

See ​http://lists.xcf.berkeley.edu/lists/gimp-developer/2007-January/017027.html.

Currently gimp2 builds without dbus support by default but this functionality can be enabled by using the +dbus variant. Perhaps this should be reversed: dbus should be enabled by default to address your issue. Could also add a variant to build gimp-remote (and disable dbus ?) for those who prefer the old method.

[devans@…]

I mis-spoke above. Gimp registers an Open method with dbus session bus at startup if no such method already exists or, if it does (because there is already a gimp instance running), it passes off its arguments to the existing instance and exits.

[edheil@…]

Whichever way works, as long as gimp-app keeps up with it, is fine with me. :)

[devans@…]

Fixed in r46775 which removes the +dbus variant and makes dbus support the default. Executing 'gimp <url>' now has the same effect as the obsolete gimp-remote helper app. Added +remote variant that will enable building of the gimp-remote app if needed for backwards compatibility with old scripts.

[anonymous]

Milestone Port Bugs deleted