Your message dated Fri, 3 May 2019 10:35:42 +0100 with message-id <03052019102626.a73312aaf...@desktop.copernicus.org.uk> and subject line Re: Bug#886335: cups: cups printer does not print postscript jobs from windows client after upgrade to stretch has caused the Debian Bug report #886335, regarding gstoraster fails with a PJL encapsulated PS document to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 886335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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) does not print jobs from windows client (configured with a generic Postscript driver, e.g. HP LaserJet 2300 Series PS) and holds the jobs... cups/error_log claims "<STDIN>: unknown file type" and "loadFile failed: temp file: not a PDF file" 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. -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8), LANGUAGE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cups depends on: ii cups-client 2.2.1-8 ii cups-common 2.2.1-8 ii cups-core-drivers 2.2.1-8 ii cups-daemon 2.2.1-8 ii cups-filters 1.11.6-3 ii cups-ppdc 2.2.1-8 ii cups-server-common 2.2.1-8 ii debconf [debconf-2.0] 1.5.61 ii ghostscript 9.20~dfsg-3.2+deb9u1 ii libavahi-client3 0.6.32-2 ii libavahi-common3 0.6.32-2 ii libc-bin 2.24-11+deb9u1 ii libc6 2.24-11+deb9u1 ii libcups2 2.2.1-8 ii libcupscgi1 2.2.1-8 ii libcupsimage2 2.2.1-8 ii libcupsmime1 2.2.1-8 ii libcupsppdc1 2.2.1-8 ii libgcc1 1:6.3.0-18 ii libstdc++6 6.3.0-18 ii libusb-1.0-0 2:1.0.21-1 ii poppler-utils 0.48.0-2 ii procps 2:3.3.12-3 Versions of packages cups recommends: ii avahi-daemon 0.6.32-2 pn colord <none> ii cups-filters [ghostscript-cups] 1.11.6-3 ii printer-driver-gutenprint 5.2.11-1+b2 Versions of packages cups suggests: ii cups-bsd 2.2.1-8 ii cups-pdf 2.6.1-22 ii foomatic-db 20161201-1 ii hplip 3.16.11+repack0-3 ii printer-driver-cups-pdf [cups-pdf] 2.6.1-22 ii printer-driver-hpcups 3.16.11+repack0-3 ii smbclient 2:4.5.12+dfsg-2+deb9u1 ii udev 232-25+deb9u1 -- Configuration Files: /etc/default/cups changed: -- debconf information: cupsys/raw-print: true cupsys/backend: lpd, socket, usb, snmp, dnssd
--- End Message ---
--- Begin Message ---On Thu 04 Jan 2018 at 16:54:43 +0100, SZABO Zsolt wrote: > 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) > > does not print jobs from windows client (configured with a generic > Postscript driver, e.g. HP LaserJet 2300 Series PS) > and holds the jobs... > > cups/error_log claims "<STDIN>: unknown file type" and > "loadFile failed: temp file: not a PDF file" > > 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" Not observed with cups-filters 1.21.6-5. It was probably fixed in 1.20.3 with - gstoraster: Improved detection whether input is PostScript or PDF by skipping over possible headers. Thanks to Rod Schmidt (schmidtrod at q dot com) for the patch. Also see the discussion spanning April/May beginning at https://lists.cups.org/pipermail/cups/2019-April/074600.html Regards, Brian.
--- End Message ---
