On Sat 21 Sep 2019 at 22:25:25 +0200, Francesco Poli wrote: > On Sat, 21 Sep 2019 19:14:07 +0100 Brian Potkin wrote: > > > On Sat 21 Sep 2019 at 17:45:06 +0200, Francesco Poli wrote: > [...] > > > Unless I am misinterpreting something, this bug seems to have vanished > > > or have been fixed in printer-driver-hpcups/3.19.8+dfsg0-1 > > > > You are not using printer-driver-hpcups. > > Am I not?!?
Not according to the PPD you used to set up the queue. > -m drv:///hpijs.drv/hp-laserjet_1320-hpijs.ppd An hpijs PPD doesn't use the hpcups filter. > > > I do not understand why other users seem to get different experiences... > > > > Perhaps you could set up a queue with printer-driver-hpcups to gain some > > understanding. > > I thought that > > # lpadmin -x lj > # lpadmin -p lj -E \ > -v 'usb://HP/LaserJet%201320%20series?serial=00CNFW522KS9' \ > -m drv:///hpijs.drv/hp-laserjet_1320-hpijs.ppd \ > -o pdftops-renderer-default=pdftops \ > -L local -D "HP LaserJet 1320" > lpadmin: Printer drivers are deprecated and will stop working in a future > version of CUPS. > # lpoptions -p lj -o media=A4 -o sides=two-sided-long-edge > # lpadmin -d lj > > did set up a queue with printer-driver-hpcups. The hp-laserjet_1320-hpijs.ppd is not in printer-driver-hpcups. > At the very least, this was the queue where I originally experienced the > bug (please remember that I am the original bug report submitter!). > And the error log said that "/usr/lib/cups/filter/hpcups" had "crashed > on signal 6". > And > > $ dpkg -S /usr/lib/cups/filter/hpcups > printer-driver-hpcups: /usr/lib/cups/filter/hpcups > > This is what made me conclude that the bug was in package > printer-driver-hpcups. It could be me who is confused. Cheers, Brian.
