Red Hat Bugzilla – Bug 90619
lpq from cups too primitive to be of a real use
Last modified: 2014-01-21 17:48:42 EST
Description of problem:
With a printer configured to use a printer on a remote (LPRng queue)
lpq from CUPS, and it graphic front end, show "no entries" immediately
after a job left a machine on which it originated even if things can
be queued on a server and a printer is really busy printing.
From another machine on the same network, for which that printer is also
"remote" but which is running LPRng, typing 'lpq' shows a real state
of a queue with a number of jobs spooled.
This has also obvious consequences for 'lprm' as there is no way to
cancel a job, even if it is tenth or twentieth in the real queue, if
there are "no entries".
follow this thread - this is, apparently, a 'feature' of cups and is
mind boggling to figure out why it acts like this or how to enable
more conventional networked-printing models
*** Bug 154117 has been marked as a duplicate of this bug. ***
*** Bug 192054 has been marked as a duplicate of this bug. ***
Fedora Core 5 is not maintained anymore.
If this bug is still present in Fedora 8 please update the version field.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.