Bug 678660 - CUPS reports printer is out of paper even though it prints
Summary: CUPS reports printer is out of paper even though it prints
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cups
Version: 6.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Tim Waugh
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 756082
TreeView+ depends on / blocked
 
Reported: 2011-02-18 20:06 UTC by Jacob Hunt
Modified: 2018-11-14 14:25 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-01 18:05:18 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jacob Hunt 2011-02-18 20:06:56 UTC
Description of problem:

Basically, the line `Reason media-empty-error` gets added to the printer in the printers.conf on the server when it runs out of paper, but never goes away, even if paper is added to the printer.

You can manually remove the lines from the printers.conf and restart cups, but the problem will just reappear again once the printer runs out of paper.

I have yet to see a Red Hat bugzilla against this problem, but came across the workaround here:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/559331

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

cups-1.4.2-35.el6_0.1.x86_64 
cups-libs-1.4.2-35.el6_0.1.i686   
cups-libs-1.4.2-35.el6_0.1.x86_64       
cups-pdf-2.5.0-4.el6.x86_64       

How reproducible:

always

Steps to Reproduce:
1. submit print job larger then amount of paper
2. when paper is out, refill paper and continue from printer
  
Actual results:

cups complains that printer is out of paper

Expected results:

Error to be cleared once paper is refilled

Additional info:

Comment 2 Tim Waugh 2011-02-23 17:06:20 UTC
This could either be a driver problem or a backend (job transport) problem.

What does this command say for the queue that exhibits this problem?:

grep ^.NickName /etc/cups/ppd/*

(This will tell us which driver is being used.)

Also, what does 'lpstat -s' say for the queue that exhibits the problem? (This will tell us which backend is being used.)

Thanks.

Comment 4 Phil Knirsch 2011-06-09 13:56:21 UTC
Any news?

Thanks & regards, Phil

Comment 8 Tim Waugh 2011-11-22 17:03:51 UTC
Please note that information is required in order to make progress on this bug report.  See comment #2.


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