Bug 678660

Summary:	CUPS reports printer is out of paper even though it prints
Product:	Red Hat Enterprise Linux 6	Reporter:	Jacob Hunt <jhunt>
Component:	cups	Assignee:	Tim Waugh <twaugh>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.0	CC:	brian, jmontleo, jwest, ngalvin, pknirsch, prc
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-01 18:05:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	756082

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.