Bug 675076 - Second page does not print correctly - overprints
Summary: Second page does not print correctly - overprints
Status: RESOLVED DUPLICATE of bug 628233
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: Printing (show other bugs)
Version: Final
Hardware: 64bit openSUSE 11.3
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Johannes Meixner
QA Contact: Johannes Meixner
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-25 14:57 UTC by Don Hughes
Modified: 2011-03-01 08:09 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Eaxample of incorrect printing (57.60 KB, application/pdf)
2011-02-25 14:57 UTC, Don Hughes 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Don Hughes 2011-02-25 14:57:49 UTC 
Created attachment 416265 [details]
Eaxample of incorrect printing

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 (.NET CLR 3.5.30729)

When printing any file the first page prints correctly.  The second page prints with multiple headings, horizontal lines, and overprinting.

Printing was working correctly in 11.2.

I have attached a .pdf file with an example.

I have tried re-installing and upgrading Cups and the drivers.

Reproducible: Always

Steps to Reproduce:
1. lpr <filename>
2.
3.
Actual Results:  
First page prints correctly all further pages are unreadable.

Expected Results:  
All pages print correctly
Comment 1 Johannes Meixner 2011-02-25 15:24:37 UTC 
I assume this is the
"Various printout failures with CUPS default 'RIPCache 8m'"
issue which is described at
http://en.opensuse.org/Portal:Printing

Please report if "RIPCache 128m" or even "RIPCache 1024m"
(the latter only if you have at least 2GB main memory)
in /etc/cups/cupsd.conf helps in your particular case.
Comment 2 Don Hughes 2011-02-25 21:08:26 UTC 
The example shown in the link sure looks like my situation.  Changing  to RIPCache 128m did not help.  However, changing to RIPCache 1024m did.  Also changing form the Simplified Gutenprint driver to the expert driver worked with the default RIPCache.