Bug 616864

Summary: Need to increase RIPCache default
Product: Red Hat Enterprise Linux 6 Reporter: Tim Waugh <twaugh>
Component: cupsAssignee: Tim Waugh <twaugh>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: azelinka, jpopelka, mhlavink, pknirsch, twaugh, ykopkova
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:bc41f4e8c01cd31f90da292d9c902722b9a39b9f
Fixed In Version: cups-1.4.2-37.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 549901 Environment:
Last Closed: 2011-05-19 14:09:15 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: 549901    
Bug Blocks:    

Description Tim Waugh 2010-07-21 15:12:40 UTC
This behaviour has also been observed on Red Hat Enterprise Linux 6.

+++ This bug was initially created as a clone of Bug #549901 +++

abrt 1.0.2 detected a crash.

How to reproduce
-----
1.cups: http://localhost:631/
2.->printers
3.->select some printer
4.maintenance->print test page
->print job stopped: "/usr/lib/cups/filter/pstops failed" = crash


Attached file: backtrace
cmdline: /usr/bin/gs -dQUIET -dDEBUG -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOMEDIAATTRS -sDEVICE=cups -sstdout=%stderr -sOUTPUTFILE=%stdout -_
component: ghostscript
executable: /usr/bin/gs
kernel: 2.6.31.9-172.fc12.x86_64
package: ghostscript-8.70-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)

--- Additional comment from mhlavink on 2009-12-22 17:59:10 EST ---

Created an attachment (id=379940)
File: backtrace

--- Additional comment from mhlavink on 2009-12-22 18:02:11 EST ---

Created an attachment (id=379945)
var/log/cups/error_log

--- Additional comment from mhlavink on 2009-12-22 18:30:49 EST ---

I'm getting the same errors when printing regular picture and print quality is set above 'photo' (this works, but 'super photo', 'ultra photo' and 'best' do not)

--- Additional comment from twaugh on 2009-12-23 05:47:33 EST ---

Please attach the file from /etc/cups/ppd/ corresponding to the queue you are using.

--- Additional comment from mhlavink on 2009-12-29 12:31:50 EST ---

Created an attachment (id=380824)
working Stylus_Photo_R285.ppd

--- Additional comment from mhlavink on 2009-12-29 12:32:52 EST ---

Created an attachment (id=380825)
broken Stylus_Photo_R285.ppd

--- Additional comment from twaugh on 2010-01-05 06:09:26 EST ---

Created an attachment (id=381737)
pstops.ps

Output from bannertops|pstops

--- Additional comment from twaugh on 2010-01-05 06:10:04 EST ---

How to reproduce it:

PPD=Stylus_Photo_R285.ppd.broken /usr/bin/gs -dQUIET -dDEBUG \
  -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOMEDIAATTRS -sDEVICE=cups \
  -sstdout=%stderr -sOUTPUTFILE=%stdout /tmp/pstops.ps

--- Additional comment from twaugh on 2010-01-05 11:42:18 EST ---

Actually this is sufficient:

/usr/bin/gs -dQUIET -dDEBUG \
  -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOMEDIAATTRS -sDEVICE=cups \
  -sstdout=%stderr -sOUTPUTFILE=%stdout /tmp/pstops.ps

--- Additional comment from twaugh on 2010-01-05 11:43:08 EST ---

Reported upstream:
  http://bugs.ghostscript.com/show_bug.cgi?id=691046

--- Additional comment from twaugh on 2010-03-16 11:32:00 EDT ---

Still occurs with ghostscript-8.71-6.fc12.

--- Additional comment from twaugh on 2010-03-23 07:22:32 EDT ---

Oh, this is to do with RIP_MAX_CACHE.  Setting RIP_MAX_CACHE to "128m" works around the problem.

--- Additional comment from twaugh on 2010-03-23 07:28:46 EDT ---

See also CUPS STR #3535, a request to change the default RIP cache size.

Comment 7 errata-xmlrpc 2011-05-19 14:09:15 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0715.html