I am setting up a Canon LBP6200 printer on USB which goes through the motionsof printing but nothing actually prints. A helpful poster on the forum set up this

sudo cupsfilter -p /etc/cups/ppf/PPD -m printer/foo -e /etc/nsswitch.conf > out.dat 2>log

and the latter part of the resulting log is

These are the filters used to process the print job. pstocapt3 is the Canon filter from the capt package.
INFO: texttopdf (PID 5077) exited with no errors.
INFO: pdftopdf (PID 5078) exited with no errors.
The first two filters complete successfully.
DEBUG: Running command line for gs: gs -q -dNOPAUSE -dBATCH -dSAFER -dNOMEDIAATTRS -sDEVICE=ps2write -dShowAcroForm -sOUTPUTFILE=%stdout -dLanguageLevel=3 -r600 -dCompressFonts=false -dNoT3CCITT -dNOINTERPOLATE -c 'save pop' -f /tmp/013d75e35ecc0
DEBUG: Started filter gs (PID 5081)
DEBUG: Started filter pstops (PID 5082)
Ghostscript (gs) is used in the third filter.
DEBUG: PID 5082 (pstops) exited with no errors.
DEBUG: PID 5081 (gs) exited with no errors.
INFO: pdftops (PID 5079) exited with no errors.
Ghostscript and the third filter complete successfully.
opvpOpenPrinter(463)
CStubOpenPrinter(397)
opvpOpenPrinter(463)
CStubOpenPrinter(397)
Error Response:ReqNo=5, SeqNo=4,opvpErrorNo=-2
Error Response:ReqNo=7, SeqNo=93,opvpErrorNo=-2
Error Response:ReqNo=8, SeqNo=1730,opvpErrorNo=-2
Error Response:ReqNo=7, SeqNo=1731,opvpErrorNo=-2
Error Response:ReqNo=8, SeqNo=1749,opvpErrorNo=-2aze.myzen.co.uk
GPL Ghostscript 9.26: Unrecoverable error, exit code 1
Error Response:ReqNo=6, SeqNo=1750,opvpErrorNo=-2
Error Response:ReqNo=3, SeqNo=1751,opvpErrorNo=-2

Can anyone explain the ghostscript error and suggest how to overcome eit?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <fdde25db-89cf-45e8-98d9-e0a7cdef20f7@googlegroups.com>, ken@balglaze.myzen.co.uk says...

Can anyone explain the ghostscript error and suggest how to overcome

eit?

You don't have the real Ghostscript error message there, just the error
code which is what it says, a fatal error.

I believe its possible to get CUPS to log the Ghostscript back channel
to get the real error message, but I can't recall how to do that. I
think there might be instructions somewhere. Hmm you could try this URL:

https://wiki.ubuntu.com/DebuggingPrintingProblems

and look for CUPS error_log where it has instructions for setting the
logging level.

If you make the file available I can look at the problem (since you have
given the command line). I doubt you can 'overcome it', most likely
either the input file is damaged or its a Ghostscript bug.

I should note that you are not using the most up to date version of Ghostscript, and there are known security problems with the version you
are using.


Ken

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)