Red Hat Bugzilla – Bug 109059
gs views a file fine, but fails when used as a renderer by Foomatic
Last modified: 2007-11-30 17:10:33 EST
I have a file that seems to be valid postscript. gs will view it just
fine, and it prints on Postscript printers without error. But when
printing to an attached HP Business Inkjet 2200 using Ghostscript as
the renderer, everything bombs with the following Ghostscript error
(sorry for wrapping):
Error: /undefined in MathWorks
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 1 3 %oparray_pop
1 3 %oparray_pop 1 3 %oparray_pop .runexec2
--nostringval-- --nostringval-- --nostringval-- 2
%stopped_push --nostringval-- --nostringval-- --nostringval--
--dict:1070/1123(ro)(G)-- --dict:0/20(G)-- --dict:101/200(L)--
Current allocation mode is local
Last OS error: 2
GNU Ghostscript 7.05: Unrecoverable error, exit code 1
I will attach the job and the full log.
This happens with Ghostscript 7.05-32.1 from Shrike and 7.07-11 from
Fedora. Foomatic is 3.0.0-6.
My first guess at the problem is that something in the extra
postscript that foomatic inserts around the document interferes with
the document itself. Unfortunately I don't know how to extract the
job that is sent to the renderer, nor do I know enough about
Postscript to be able to debug it if I could find it. I was informed
on Usenet that the job prints fine when ESP Ghostscript is used as the
renderer, but my attempts to get it properly installed have failed.
Created attachment 95717 [details]
Job which fails to print
Created attachment 95718 [details]
Full CUPS logfile
Much debugging effort showed this to be a problem not in Ghostscript
but in Foomatic. The modifications it made resulted in an invalid
Postscript file. Upgrading to the foomatic-rip in
foomatic-filters-3.0-20031104 fixed the problem.
Changing the component to foomatic as that's where the bug is.
Fixed in foomatic-3.0.0-10.