Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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