Comment 44 for bug 978120

Huh, debug option doesn't do everything I thought it did - never mind, that gave me enough I could get what I need with a little manual hacking.

First of all, your printer is broken!!! Four different Postscript interpreters, all from different vendors (include Adobe) all agree that this is valid, conforming Postscript, and interpret and render the file just fine.

Thus, your first port of call really should be the printer vendor - the printer is faulty!

Anyway, here is a version of the file with the same content as the Ghostscript one you supplied, but with all the compression removed:
http://www.ghostscript.com/~chrisl/ko-nodebug-cut001.ps

You need to send this to your printer using the following command:

lpr -P <printer name> -oraw ko-nodebug-cut001.ps

(the "-oraw" bypasses the cups filters, and sends the file straight through)

Once you have done this, can you confirm (or otherwise) that "ko-nodebug-cut001.ps" still causes the same error on your printer as before.

BTW, as this could be a protracted process, is there a preferable communications channel for you? E-mail, or whatever?

Chris