Bug#810474: cups: Unable to clear print queue

[Brian Potkin <claremont102@gmail.com>]

On Tue 12 Jan 2016 at 13:00:56 -0800, David Christensen wrote:

> On 01/12/2016 08:15 AM, Brian Potkin wrote:
> 
> >To test, set up a print queue with
> >
> >   lpadmin -p test -v ipp://192.168.7.19 -E
> 
> $ sudo lpadmin -p test -v ipp://192.168.7.19 -E
> 
> >and print to it with
> >
> >   lp -d <file>
> 
> $ lp -d Data/dpchrist/Downloads/f/fsf/licenses/gpl-2.txt
> WARNING: gnome-keyring:: couldn't connect to:
> /home/dpchrist/.cache/keyring-oIagOw/pkcs11: No such file or directory
> lp: The printer or class does not exist.
> 
> >The printer doesn't exist, so the command
> >
> >   lpstat
> 
> $ lpstat
> WARNING: gnome-keyring:: couldn't connect to:
> /home/dpchrist/.cache/keyring-oIagOw/pkcs11: No such file or directory
> 
> >as a user should show the job as being queued.
> >
> >   cancel -a
> 
> $ sudo cancel -a
> 
> >as root should remove the job from the queue. This is shown by
> >
> >   lpstat
> 
> $ lpstat
> WARNING: gnome-keyring:: couldn't connect to:
> /home/dpchrist/.cache/keyring-oIagOw/pkcs11: No such file or directory

I am unfamiliar with how gnome-keyring operates but these are only
warnings and 'cancel -a' might have completed. 'ls -l /var/spool/cups'
before and after the command should show what happens to any file
beginning with "d" in the spool.

Alternatively, log out of the DE and work in a console.

> >   ls -l /var/spool/cups
> 
> $ sudo ls -l /var/spool/cups
> total 4
> drwxrwx--T 2 root lp 4096 Jan 11 12:08 tmp

Empty now. The question is - what was there before 'cancel -a'?

> >and, with debug logging set, the error log.
> 
> Where is the error log?

/var/log/cups.