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 504732 - Eps plugin dialog freezes
Eps plugin dialog freezes
Status: RESOLVED NOTGNOME
Product: GIMP
Classification: Other
Component: Plugins
2.4.x
Other Mac OS
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2007-12-20 19:50 UTC by Christoph
Modified: 2008-10-30 20:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screenshot of the progressbar of an eps import (59.10 KB, image/png)
2007-12-20 20:01 UTC, Christoph
Details
gs is started (58.31 KB, image/png)
2007-12-20 20:27 UTC, Christoph
Details

Description Christoph 2007-12-20 19:50:03 UTC
Hi there.

On Macaintosh opening a eps file brings up the import dialog, but then the progress bar freezes.

Running gimp 2.4.3 and GPL Ghostscript 8.61 (2007-11-21)
Comment 1 Sven Neumann 2007-12-20 19:58:20 UTC
There shouldn't be a progress bar at all when the dialog is brought up. Perhaps you can explain this better? A screen-shot might help.
Comment 2 Christoph 2007-12-20 20:01:04 UTC
Created attachment 101343 [details]
screenshot of the progressbar of an eps import
Comment 3 Sven Neumann 2007-12-20 20:22:07 UTC
Ok, so the freeze happens after the user has confirmed the Postscript plug-in dialog. At this point the plug-in waits for input from the Ghostscript process. Can you check if that process has been started and if it is running?
Comment 4 Christoph 2007-12-20 20:27:36 UTC
Created attachment 101352 [details]
gs is started

gs is started after i press import.
Comment 5 Christoph 2007-12-20 20:29:39 UTC
I just checked. We also had this problem with gimp 2.4.2. I don't know if this is maybe a gs error. I can open a file with gs via the terminal.

I really don't have the knownledge about these things, so sorry if I act a little dumb here.
Comment 6 Sven Neumann 2007-12-20 20:35:47 UTC
Well, it looks like a communication problem between the postscript plug-in and gs. They are supposed to talk to each other over a pipe. This should actually work on Mac OS X, but it looks like there's a problem. Perhaps the problem is in gs, perhaps in the plug-in. As a workaround you could define USE_REAL_OUTPUTFILE in postscript.c, as it is done for Win32.

Comment 7 Christoph 2007-12-20 20:37:15 UTC
I will also commit the "bug" to Macports. I know that it worked with previous versions. thanks. 
Comment 8 Sven Neumann 2007-12-21 09:32:21 UTC
Does using the #define I told you about solve the problem?
Comment 9 Christoph 2007-12-21 15:50:10 UTC
Yes, but i does not change anything.

Just to make it clear. i change the phostscript.c in the source and then compile the gimp? 
That's what i did.
Comment 10 Sven Neumann 2007-12-21 17:03:37 UTC
If that doesn't change anything then the problem is not the communication over the pipe. Looks like gs is not producing any output. Since we didn't change anything in the postscript plug-in since 2.4.0 was released, this appears to be a problem with your build or with Ghostscript.
Comment 11 Christoph 2007-12-21 17:04:55 UTC
I also think so. We try to fix it. Thanks for your help