Red Hat Bugzilla – Bug 170422
Cups won't retry printing after a problem
Last modified: 2008-08-02 19:40:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
Description of problem:
Sometimes the print queue stops printing. Lpq shows something like:
printer lp is not ready
Printing will not resume until root issues the command: /usr/bin/enable lp
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Keep printing jobs
2.Wait for printer not ready to show up in lpq
3.Printer won't start again until the enable command is issued
Actual Results: After the enable command, printing resumes until sometime in the future when it
stops again. This happens occasionally, but seems to occur on all of our computers eventually.
Expected Results: The printer not ready statement should never occur unless a disable command is specifically given. If the printer is out of paper or out of toner, the appropriate error message should appear. The cups daemon should automatically be trying to print to any printer with a problem until the printing goes through successfully. This is the way it used to work under the RedHat operating systems.
This problem also occurs in FC3 - not sure if it occurred in FC2 (we only ran FC2 on a single machine for a short period of time). I'm pretty sure that it didn't occur in FC1 and am positive that it never occurred under RedHat.
This backend can do what you need:
I would love to incorporate this automatically into the system-config-printer
configuration program, but it needs redesigning for that.
So, I'll set the bug for redesigning it as blocking this.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
The error policy can now be set using System->Administration->Printing,
selecting the printer, then the 'Policies' tab, and choosing an error policy.
The default is stop-printer but abort-job and retry-job are alternatives.
Now that the Policy can be set, this bug can be eliminated.