Bug#860591: cups-daemon: Job enters queue, then stops and can't be removed
On Thu 20 Apr 2017 at 06:32:08 +1000, Ben Finney wrote:
> On 19-Apr-2017, Brian Potkin wrote:
> > On Wed 19 Apr 2017 at 21:09:52 +1000, Ben Finney wrote:
> >
> > > =====
> > > $ 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.
>
> How can you tell that a job doesn't get that far?
It would have printed. You record that it didn't. Assuming the device is
correct and wireless and printer are working soundly.
> > > device for PDF: cups-pdf:/
> > > device for SCX-4623-Series: usb://Samsung/SCX-4623%20Series?serial=Z2WUBFFZ300396N&interface=1
> >
> > A local connection. Looks ok.
>
> This is the printer queue which worked fine until early 2017.
>
> > > 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.
>
> Every job that I submit now gets stuck like this.
>
> > 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.
>
> =====
> $ sudo ls -l /var/spool/cups/
> total 4
> drwxrwx--T 2 root lp 4096 Apr 20 06:21 tmp
>
> [… submit a Test Page job using GNOME 3's control center …]
>
> $ sudo ls -l /var/spool/cups/
> total 12
> -rw------- 1 root lp 970 Apr 20 06:23 c00066
> -rw-r----- 1 root lp 234 Apr 20 06:23 d00066-001
> drwxrwx--T 2 root lp 4096 Apr 20 06:23 tmp
>
> $ lpstat -t
> $ lpstat -t
> scheduler is running
> system default destination: SCX-4623-Series
> […]
> SCX-4623-Series accepting requests since Thu 20 Apr 2017 06:23:15 AEST
> […]
> printer SCX-4623-Series now printing SCX-4623-Series-66. enabled since Thu 20 Apr 2017 06:23:15 AEST
> Waiting for printer to become available.
> […]
> SCX-4623-Series-66 bignose 1024 Thu 20 Apr 2017 06:23:15 AEST
>
> $ cancel -a -x
>
> $ sudo ls -l /var/spool/cups/
> total 8
> -rw------- 1 root lp 970 Apr 20 06:23 c00066
> drwxrwx--T 2 root lp 4096 Apr 20 06:23 tmp
>
The d file has been removed from the queue.
> =====
>
> > Set up this print queue (as root):
> >
> > lpadmin -p testq -v /home/<user>/testq-out -E -P </etc/cups/ppd/<PPD_for_the_Samsung>
>
> Hasn't that already been done?
No. Note the different device-uri (-v). However, it is incorrect; change
it to "-v file:/home/<user>/testq-out". The idea is to discover whether
the job goes through the filtering system.
> I initially set up this print queue using GNOME 3 control center. I
> didn't need to specify any PPD manually.
>
> The printer has been working unchanged for years until early 2017. Are
> you saying I need to remove it and start again? I would prefer to
> diagnose what's wrong, so that this problem can be fixed for others
> too.
I haven't said anything about removing your present queues as part of
the suggested outlined diagnostic approch.
Regards,
Brian.
Reply to: