Bug#248947: cupsys: gs crash, no pages output

[Jonathan Nieder]

tags 248947 + upstream moreinfo
retitle 248947 ghostscript: Error: /typecheck in --.unread-- printing 
postscript documents
quit

Derrick 'dman' Hudson wrote:

> I can no longer print postscript documents.  Tonight is the first time
> I tried printing since the last package upgrade.  (although I did
> print a pdf earlier tonight.  I guess it only affects postscript)  The
> error log reports the following:
[...]
> Error: /typecheck in --.unread--

Hmm.  Unfortunately this is a vague message; I suspect it represents
an error in the command line options.  Some internet sightings:

Using ps2pdf on a filename with spaces. [1]  That one was fixed by Tim
Waugh in ghostscript-7.20~256.

The ImageMagick identify and convert[2][3] utilities once provoked
this in some way.

Use of an unknown option[4] (for example, due to a mismatch between
expected and actual ghostscript version) can also provoke it.

[1] http://www.ghostscript.com/pipermail/bug-gs/2003-June/003222.html
[2] 
http://studio.imagemagick.org/pipermail/magick-users/2003-September/010856.html
[3] http://studio.imagemagick.org/pipermail/magick-users/2003-June/009642.html
[4] http://groups.google.com/group/comp.text.tex/msg/4d432d65f7b5d777




-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110123020532.GA27463@burratino

Bug#248947: cupsys: gs crash, no pages output

[Jonathan Nieder]

Hi Derrick,

Derrick 'dman' Hudson wrote:
> On Fri, May 14, 2004 at 12:49:29PM +0900, Kenshi Muto wrote:
>| Derrick 'dman' Hudson wrote:

>|> D [13/May/2004:21:23:22 -0400] [Job 2910] Error: /typecheck in --.unread--
>|> D [13/May/2004:21:23:22 -0400] [Job 2910] Operand stack:
>|> D [13/May/2004:21:23:22 -0400] [Job 2910] true   --nostringval--   true   0
>|> D [13/May/2004:21:23:22 -0400] [Job 2910] Execution stack:
>|> D [13/May/2004:21:23:22 -0400] [Job 2910] %interp_exit   .runexec2   
>--nostringval--   --nostringval--   --nostringval--   2   %stopped_push   
>--nostringval--   --nostringval--   --nostringval--   false   1   
>%stopped_push   1   3   %oparray_pop   --nostringval--   1   1   3   
>--nostringval--   %for_pos_int_continue   --nostringval--   --nostringval--   
>--nostringval--
[...]
> The documents that wouldn't print all came from Mozilla Firefox
> (0.8-8).  The PDF I printed earlier last night was generated by
> pdflatex.

Thank you.  Are you still able to reproduce this problem?  If so,
could you send a postscript document that fails, for example by asking
firefox to "print to file"?

[...]
> In case it will help you, I am posting one of the PS documents and
> both PPD files :
> 
> PS Document - http://dman13.dyndns.org/~dman/Bug248947/Document.ps
> PPD Home- http://dman13.dyndns.org/~dman/Bug248947/ljet3.ppd
> PPD Work- http://dman13.dyndns.org/~dman/Bug248947/ljet5.ppd

That does sound helpful, but it looks like it has been taken down.

Regards,
Jonathan




-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110115085757.GA27118@burratino