On Wed 19 Apr 2017 at 21:09:52 +1000, Ben Finney wrote: > On 19-Apr-2017, Brian Potkin wrote: > > > The printer make and model, please. > > This occurs with both printers I have available. > > Samsung SCX-4623F > HP LaserJet Pro MFP-M227fdw > > Earlier versions (Debian Stretch, mid-to-late 2016) of CUPS on this > host were working fine with the Samsung printer. > > > lpstat -t > > lpoptions -p <queue_name> > > ===== > $ lpstat -t > scheduler is running > system default destination: SCX-4623-Series > device for HP-LaserJet-MFP-M227-M231: > dnssd://HP%20LaserJet%20MFP%20M227fdw%20(09EB59)._ipp._tcp.local/?uuid=564e4333-3930-3031-3137-98e7f409eb59
There is a direct connection to the printer via its Airprint facilty, No other CUPS server is involved. A job doesn't get as far as using the device. > device for PDF: cups-pdf:/ > device for SCX-4623-Series: > usb://Samsung/SCX-4623%20Series?serial=Z2WUBFFZ300396N&interface=1 A local connection. Looks ok. > device for XP-310: > usb://EPSON/XP-310%20Series?serial=533538503030343819&interface=1 > device for XP-310-Series: > usb://EPSON/XP-310%20Series?serial=533538503030343819&interface=1 > HP-LaserJet-MFP-M227-M231 accepting requests since Tue 18 Apr 2017 20:33:31 > AEST > PDF accepting requests since Tue 18 Apr 2017 20:22:05 AEST > SCX-4623-Series accepting requests since Wed 19 Apr 2017 21:03:20 AEST > XP-310 accepting requests since Fri 30 Dec 2016 12:00:16 AEDT > XP-310-Series accepting requests since Fri 30 Dec 2016 12:00:16 AEDT > printer HP-LaserJet-MFP-M227-M231 is idle. enabled since Tue 18 Apr 2017 > 20:33:31 AEST > printer PDF is idle. enabled since Tue 18 Apr 2017 20:22:05 AEST > printer SCX-4623-Series now printing SCX-4623-Series-65. enabled since Wed > 19 Apr 2017 21:03:20 AEST > Waiting for printer to become available. This is a stuck job. > printer XP-310 disabled since Fri 30 Dec 2016 12:00:16 AEDT - > Unplugged or turned off > printer XP-310-Series disabled since Fri 30 Dec 2016 12:00:16 AEDT - > Unplugged or turned off > HP-LaserJet-MFP-M227-M231-64 bignose 1024 Tue 18 Apr 2017 > 20:33:29 AEST > SCX-4623-Series-65 bignose 1024 Wed 19 Apr 2017 21:03:20 AEST You should be able to cancel the stuck job and clear the last two lines with 'cancel -a -x'. Check /var/spool/cups before and after the command. > $ lpoptions -p SCX-4623-Series > copies=1 > device-uri=usb://Samsung/SCX-4623%20Series?serial=Z2WUBFFZ300396N&interface=1 > finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 > job-sheets=none,none marker-change-time=0 number-up=1 printer-commands=none > printer-info='Samsung SCX-4623 Series' printer-is-accepting-jobs=true > printer-is-shared=true printer-location=lantana > printer-make-and-model='Samsung SCX-4623f, 2.0.0' printer-state=4 > printer-state-change-time=1492599800 printer-state-reasons=none > printer-type=143428 > printer-uri-supported=ipp://localhost/printers/SCX-4623-Series > > $ lpoptions -p HP-LaserJet-MFP-M227-M231 > copies=1 > device-uri=dnssd://HP%20LaserJet%20MFP%20M227fdw%20(09EB59)._ipp._tcp.local/?uuid=564e4333-3930-3031-3137-98e7f409eb59 > finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 > job-sheets=none,none marker-change-time=1492511611 > marker-colors=#000000,none,none,none,none marker-levels=97,-1,-1,-1,100 > marker-names='Black\ Cartridge\ HP\ CF230A,,,,Imaging\ Drum\ HP\ CF232A' > marker-types=toner,unknown,unknown,unknown,opc number-up=1 > printer-commands=none printer-info='HP LaserJet MFP M227fdw (09EB59)' > printer-is-accepting-jobs=true printer-is-shared=true printer-location > printer-make-and-model='HP LaserJet MFP m129-m134, hpcups 3.16.11' > printer-state=3 printer-state-change-time=1492511611 > printer-state-reasons=none printer-type=36876 > printer-uri-supported=ipp://localhost/printers/HP-LaserJet-MFP-M227-M231 Set up this print queue (as root): lpadmin -p testq -v /home/<user>/testq-out -E -P </etc/cups/ppd/<PPD_for_the_Samsung> See the Printing section of the wiki on how to enable debug logging. Print something to the queue and send a compressed error_log here. Does a file appear in /home/<user>/? Cheers, Brian.
