After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 555362 - gimp-remote is not working properly
gimp-remote is not working properly
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: General
git master
Other All
: Normal minor
: 2.6
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2008-10-07 09:04 UTC by Mike
Modified: 2008-10-08 16:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mike 2008-10-07 09:04:36 UTC
Please describe the problem:
Starting gimp with gimp-remote works, but when gimp is already running gimp-remote doesn't open the called image I just get " Es konnte keine Verbindung zu GIMP hergestellt werden. Bitte stellen Sie sicher, dass der Werkzeugkasten sichtbar ist!" on the Terminal.
I'm working on the latestest Ubuntu 8.10 and gimp svn.

greets mike

Steps to reproduce:
1. gimp-remote test.jpg & (works)
2. gimp-remote test2.jpg & (doesn't open test2.jpg but gives the output)
3. 


Actual results:


Expected results:
Called Image should be opened...

Does this happen every time?
Yes

Other information:
Comment 1 Martin Nordholts 2008-10-07 16:30:20 UTC
There is no need to use gimp-remote, simply start with the normal gimp binary.
Comment 2 Sven Neumann 2008-10-07 20:41:50 UTC
gimp-remote is deprecated as it is not any longer needed. It is not even built by default. If there are any problems with it, we are not likely going to fix them.
Comment 3 Sven Neumann 2008-10-07 20:54:20 UTC
It should still work though and I just confirmed that it doesn't.
Comment 4 Michael Natterer 2008-10-07 21:10:56 UTC
Fixed in SVN:

2008-10-07  Michael Natterer  <mitch@gimp.org>

	Bug 555362 – gimp-remote is not working properly

	* app/widgets/gimptoolbox-dnd.c (gimp_toolbox_dnd_init): add the
	window itself as drop traget again so gimp-remote works.
Comment 5 Mike 2008-10-07 21:47:38 UTC
Thanks for fixing!

The problem with the "gimp" command is, that it loads a new instance of gimp... I need it for use with ufraw, which gives a very convenient RAW-photography workflow... so is there a possibility, to load several images (one after another) with the "gimp" command in the same gimp instance... I only see a swith for generating a new instance...

Thanks again.

Greets, mike
Comment 6 Sven Neumann 2008-10-08 06:39:50 UTC
Mike, in case you did not realize yet. The gimp executable provides the same functionality as gimp-remote used to provide. It will check if there's another instance running and delegate to that instance. If that doesn't work for you, then your copy of gimp was built without support for the D-Bus message protocol and you should rather fix that than using gimp-remote. At some point gimp-remote will be completely removed.
Comment 7 Mike 2008-10-08 16:46:49 UTC
Sorry Sven, I have to ask again. 
gimp-remote works properly now, but my gimp is built with DBUS support and it still opens a new window... Should I open a new bug report for that?

Greets, Mike