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 742133 - Cannot Open EPS file
Cannot Open EPS file
Status: RESOLVED DUPLICATE of bug 736811
Product: GIMP
Classification: Other
Component: General
2.8.14
Other Windows
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2014-12-31 01:00 UTC by billbledsoe
Modified: 2015-01-09 14:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description billbledsoe 2014-12-31 01:00:17 UTC 
Steps:
Open GIMP 2
Select > File > Open Image
Select an EPS file

Windows Error message appears:
GNU Image Manipulation Program Plug-in has stopped working
A problem caused the program to stop working correctly. Pleas close the program. 

-> Close Program

Clicking Close Program produces the following GIMP Error Messages: 

GIMP Message:
Plug-in crashed: "file-ps.exe"
(C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins\file-ps.exe)

The dying plug-in may have messed up GIMP's internal state. You may want to save your images and restart GIMP to be on the safe side.

GIMP Message:
Opening 'C:\Users\Documents\my stuff\123.eps' failed:

Procedure 'file-eps-load' returned no return values

OK

Clicking OK returns me to GIMP in the state I left GIMP in:(Open Image dialog box open)

Able to repeat this with MULTIPLE EPS files, 100% of the time.
Comment 1 Simon Müller 2015-01-09 11:47:19 UTC 
Can confirm. EPS export works with no problems, import screws everything up. 
Workaround:

Install Ghostscript (check whether you have a 64 or 32 bit system) from http://www.ghostscript.com/download/gsdnld.html

Find C:\Program Files\gs\gsx.yy\bin\gsdllzz.dll, (ghostscript-Version: x.yy, zz is your systems bit number), copy it and rename it to libgs-8.dll. 

Put your new libgs-8.dll into C:\Program Files\GIMP 2\bin\, replacing the old file and you should be done. 

Also this should be an installer bug (at least I think so).
Comment 2 Michael Schumacher 2015-01-09 14:33:02 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 736811 ***