Bug 571353

Summary:	CUPS page_log stays empty
Product:	Red Hat Enterprise Linux 5	Reporter:	Dennixx <voetelink>
Component:	cups	Assignee:	Tim Waugh <twaugh>
Status:	CLOSED CANTFIX	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.4	CC:	jpopelka, voetelink
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:	2010-08-23 10:41:32 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:

Description Dennixx 2010-03-08 09:14:26 UTC

* Description of problem:
Last week I migrated our CUPS server to a new system with RHEL5 and all errata updates.

Everything seems to work fine, except that the /var/log/cups/page_log stays empty.
I configured the PageLog cupsd.conf configuration entry (although it should be set by default according to the comments in the file).
The file stays empty.

* Version-Release number of selected component (if applicable):
cups-1.3.7-11.el5_4.6 x86_64

* How reproducible:
I configured CUPS on another (fully updated) RHEL5 system, and there too the page_log stays empty.
 
* Actual results:
Empty /var/log/cups/page_log

* Expected results:
Every printed job should be reported in this file.

Comment 1 Dennixx 2010-04-09 13:27:08 UTC

The problem seems to have been caused by the following lines in the NRG/Ricoh PPD files (which I downloaded from openprinting.org):

-----
*cupsFilter: "application/vnd.cups-postscript 0 foomatic-rip"

*FoomaticRIPCommandLine: "printf &quot;%%!PS-Adobe-3.0\n%%%% %%&&
%%\n%B%C%D%A&quot;%%%%; cat;"
*End
-----

We had problems that some types of printjobs would hang the printers. After removing the lines mentioned from the PPD files, the printjobs would get printed without problems. At the same time, the page_log started getting filled too....

Comment 2 Tim Waugh 2010-04-21 12:30:04 UTC

Could you please attach the PPD file that was causing problems, or a pointer to it?  Thanks.

Comment 3 Dennixx 2010-04-21 13:06:51 UTC

One of the PPD's creating the problem:
http://www.openprinting.org/printer/NRG/NRG-DSc338

Comment 4 Tim Waugh 2010-08-23 10:41:32 UTC

I think this is a problem with the Ricoh PPDs.  They would be better without the foomatic-rip lines I think.