eps file cannot be opened in command line, but opens just fine in GUI

[Daniel Cordeiro]

Binary package hint: inkscape

Hi,

I have a .eps file that Inkscape can open if I'm using the GUI and click on "File / Open", but can not if I call inkscape on command line.

When I call Inkscape passing the file in command line ("$ inkscape <file.eps>"), I get the following error message:

ps2pdf failed:

Error: /undefinedfilename in (graph-cmax-10.eps)
Operand stack:

Execution stack:
   %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push
Dictionary stack:
   --dict:1157/1684(ro)(G)-- --dict:0/20(G)-- --dict:70/200(L)--
Current allocation mode is local
Last OS error: 2
GPL Ghostscript 8.71: Unrecoverable error, exit code 1

I'm sending the .eps that triggers this inconsistent behavior of Inkscape as an attachment.

Best regards,
Daniel

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: inkscape 0.48.0-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-26.46-generic 2.6.35.10
Uname: Linux 2.6.35-26-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Feb 4 14:10:56 2011
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=pt_BR.utf8
 LANGUAGE=pt_BR:en
SourcePackage: inkscape

[Alex Valavanis (valavanisalex)]

Confirmed in natty with inkscape_0.48.1-0ubuntu1. Actually, I don't appear to be able to open any EPS files from the command line.

@Daniel - do you just experience the problem with this particular file, or with every EPS document?

[su_v (suv-lp)]

Duplicate of bug #695120 “cannot open relative paths using script extensions from command line” (regression in 0.48)?

[Alex Valavanis (valavanisalex)]

Yes, I am able to open the file (and others) if I use an absolute path. I think it probably is a duplicate of bug #695120.

@Daniel - please could you try changing to the directory which contains the file, and then using:

$ inkscape `pwd`/graph-cmax-10.eps

[Daniel Cordeiro (dcordeiro)]

Hi, I just have tested and it is definitively bug #695120.
Thanks!