Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 121983 - CUPS retrying print jobs
CUPS retrying print jobs
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2004-04-29 10:46 EDT by Mike Allerhand
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-04-24 16:18:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike Allerhand 2004-04-29 10:46:07 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
Using cups-1.1.19-13 under FC1, 
every so often a job requested just once will print multiple times,
(until the paper runs out). I have raw queues that send jobs from
Windows boxes via Samba print shares to JetDirect (HP LasetJet 4100)
using IPP. When printing multiple times the CUPS web interface for
the printer says:
"Printer is busy; retrying print job..."

I tried disabling keepalive (in cupsd.conf) because I think JetDirect
does not properly support it, but this does not fix my problem.

The queues are configured using the CUPS web interface.
printconf says "Can't understand deviceURI", (see bug #82892 and 
#100796), because redhat-config-printer does not support IPP uri's.
printconf-tui --Xexport does not report any IPP queues.

Version-Release number of selected component (if applicable):

How reproducible:
Couldn't Reproduce

Additional info:
Comment 1 Tim Waugh 2004-04-30 09:10:31 EDT
Could you try the version of CUPS in the current Fedora development
repository please?  It contains changes that I think might fix the

Comment 2 Tim Waugh 2004-05-24 10:35:19 EDT
Comment 3 Tim Waugh 2005-09-08 12:46:22 EDT
Do you still see this problem?
Comment 4 John Thacker 2006-04-24 16:18:36 EDT
Closing due to lack of user response for two years.

Note You need to log in before you can comment on or make changes to this bug.