Web page 'Jobs' page shows only one job

[John A. Murdie]

> John A. Murdie wrote:
> > A user here has complained that (with CUPS 1.2.5) when he issues
> > several lp(1) commands in reasonably quick succession, the web page
> > 'Jobs' list page shows only his top job (for that printer). Only when
> > that job has been printed does the next one appear in the web
> > listing. I've reproduced this problem. No report like this is in the
> > bugs list or in the list of fixes for 1.2.6 and 1.2.7. Is it meant to
> > work like this?
>
> No, you should see all of the pending jobs on the active job list.
>
> > Oddly, another CUPS 1.2.5 server we have on another machine does show
> > multiple entries in a queue for one user - differently-named files.
> >
> > Is this something configurable that I might have set incorrectly
> > without realising it? (But I've searched the cupsd.conf help file
> > without success.) I can't believe that this is not something silly I
> > have done.
>
> No, I'd guess you are running into something specific to that system.
> Make sure the two systems have the same software installed...
>
> --
> ______________________________________________________________________
> Michael Sweet, Easy Software Products           mike at easysw dot com
> Internet Printing and Document Software          http://www.easysw.com

I managed to reproduce this error, though I don't have an explanation of why it occurs. Perhaps you (Mike), with your knowledge of the CUPS internals, will quickly see why it happened to me.

When I installed successive versions of CUPS, 1.2.3, 1.2.4, 1.2.5 and 1.2.7 (I skipped 1.2.6!) I stopped the old cupsd and then, to preserve the page.log file, I used the command e.g. 'mv /spool/cups-1.2.5 /spool/cups-1.2.7' rather than 'cd /spool/cups-1.2.7; cp ../cups-1.2.5/log/cups/page.log .' (and then started the new cupsd). Amazingly, this gives rise to the effect I describe above. (I can't be sure that I've not simply been bringing forward some once-corrupted cups variable state directory each time - how could I tell, if so?)

On the system that didn't suffer the problem I had done a fresh, first-time, install.

John A. Murdie