Ubuntu
cups-filters package

  1. Bug #998087
  2. Comment #8

Comment 8 for bug 998087

Revision history for this message
steve.horsley (steve-horsley) wrote : Re: [Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
  • stream1.raw Edit (132.9 KiB, text/plain; charset=UTF-8; name="stream1.raw")
  • stream2.raw Edit (237 bytes, application/octet-stream; name="stream2.raw")

Chris,

Thanks for looking at this for me.
I'll do what I can to help, but will probably need leading by the nose.

Till has sent me info on a proposed change to allow switching between
Poppler and GhostScript. I'll have a stab at that, but I guess you want
your sample postscript file before I start messing things up.

I'm not sure how to capture a failing .ps file for you. My first guess
was to do a print-to-file from and editor called geany. I edited a small
text file, then chose File, Print, Print to File, Postscript and saved
to my desktop. This file looks fine in Evince, and prints perfectly when
I do use netcat to send it directly to the printer. What's more, it says
"Creator: cairo 1.10.2" so I guess it's not what you're looking for.

Then I captured the TCP conversation with wireshark. This one says
"Creator: GPL Ghostscript 905 (ps2write)" so I guess it's what you're
after. I attach two files. The first one is what the PC sent to the
printer, and the second is the reply the printer sent back. The printer
did not reply until all the print was sent - there was no overlap.

Please let me know if this is OK, and I'll start messing around with
Till's update.

Steve

On 16/05/12 12:47, cliddell wrote:
> Steve,
>
> Till is looking into the possibility of providing an option to use the
> poppler tool as a workaround, I'll leave it to him to update on that
> when/if he has news.
>
> Obviously, in the long term, we'd like to resolve these issues that
> various printers have with the Postscript output from Ghostscript - note
> that Adobe CPSI consumes the GS output just fine, as does Adobe's
> Distiller, and several other Postscript interpreters.
>
> If I could ask you to attach a Postscript file here on which your
> printer gives this error - hopefully, Till can post the instructions on
> how to do that.
>
> After that, if you are willing, I'd like to give you some (possibly
> many!) Postscript files to send to your printer, to see if we can
> establish for sure what the problem is - if we can.
>
> Chris
>