[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#359821: gs: ghostcript dies when printing to epson r300, but not hp lj1200



On Wed, Mar 29, 2006 at 10:15:47AM +0100, Roger Leigh wrote:
> Kenward Vaughan <kay_jay@earthlink.net> writes:
> 
> > On upgrading this week, the epson printer stopped working.  Putting CUPS on
> > debug mode showed ghostscript failing, so I assume this is the weak point. 
> > Gutenprint may be another possibility.
> 
> This isn't a Gutenprint error; it never received any data:

I suggested it only because I hadn't looked at the entire sequence in
the log prior to the error--it struck me that Gutenprint may have been
involved in an earlier step leading into the actual point of collapse.
 

> > D [26/Mar/2006:22:10:11 -0800] [Job 3452] Error: /ioerror in --image--
> > D [26/Mar/2006:22:10:11 -0800] [Job 3452] Operand stack:
> > D [26/Mar/2006:22:10:11 -0800] [Job 3452] 
> > D [26/Mar/2006:22:10:11 -0800] [Job 3452] Execution stack:
> > D [26/Mar/2006:22:10:11 -0800] [Job 3452] %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   1   3   %oparray_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   1   11   %oparray_pop
> > D [26/Mar/2006:22:10:11 -0800] [Job 3452] Dictionary stack:
> > D [26/Mar/2006:22:10:11 -0800] [Job 3452] --dict:1119/1686(ro)(G)--   --dict:0/20(G)--   --dict:85/200(L)--   --dict:63/75(L)--   --dict:18/24(L)--   --dict:2/15(L)--   --dict:0/15(L)--   --dict:0/15(L)--   --dict:5/15(L)--   --dict:0/15(L)--   --dict:0/15(L)--
> > D [26/Mar/2006:22:10:11 -0800] [Job 3452] Current allocation mode is local
> > D [26/Mar/2006:22:10:11 -0800] [Job 3452] Last OS error: 28
> > D [26/Mar/2006:22:10:11 -0800] [Job 3452] ESP Ghostscript 815.01: Unrecoverable error, exit code 1
> 
> If you set LogLevel to debug in cupsd.conf, you will be able to see
> which process the error comes from (though it's pretty certain to come
> From Ghostscript, probably gs-esp rather than gs).

That's exactly what the above came from.  The maintainer for the 2
packages (gs and gs-esp) is the same person (Masayuki Hatta).


Kenward
-- 
In a completely rational society, the best of us would aspire to be 
_teachers_ and the rest of us would have to settle for something less, 
because passing civilization along from one generation to the next 
ought to be the highest honor and the highest responsibility anyone 
could have.     - Lee Iacocca





Reply to: