Bug#886335: cups: cups printer does not print postscript jobs from windows client after upgrade to stretch
Thank you for your report, Zsolt.
On Thu 04 Jan 2018 at 16:54:43 +0100, SZABO Zsolt wrote:
> Package: cups
> Version: 2.2.1-8
> Severity: normal
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> After upgrade to stretch the shared cups printer, an HP P1102
> (configured as: lpadmin -p HP_P1102 \
> -v usb://HP/LaserJet%20Professional%20P1102?serial=000000000Q80NARFPR1a \
> -m foo2zjs:0/ppd/foo2zjs/HP-LaserJet_Pro_P1102.ppd -E)
If it is of interest, hplip (with the plugin) also supports this
printer.
> does not print jobs from windows client (configured with a generic
> Postscript driver, e.g. HP LaserJet 2300 Series PS)
> and holds the jobs...
I do not have a Windows machine so am unable to test this part of the
process.
> cups/error_log claims "<STDIN>: unknown file type" and
> "loadFile failed: temp file: not a PDF file"
Please let us have an error_log. The Printing section of the wiki gives
details on what to do (DissectingandDebuggingtheCUPSPrintingSystem).
Compress it before sending.
> Local printing from the linux host has no problem
> (the same printer queue is intended to be used from the local linux host and
> from the clients on the subnet, i.e. setting up as a "raw" queue is not an
> option, I guess)
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> I have also tried to (re)configure the printer under another queue name
> on the cups web UI, but without any progress...
>
> * What was the outcome of this action?
>
> The same: print jobs from windows client were held with "unknown file type"
>
> * What outcome did you expect instead?
>
> Printed test pages.
Capture the file sent by the Windows machine and identify it.
Regards,
Brian.
Reply to: