Bug 639593

Summary: [abrt] ghostscript-8.71-10.fc13: cmd_put_list_op: Process /usr/bin/gs was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Charlie Bennett <ccb>
Component: ghostscriptAssignee: Tim Waugh <twaugh>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:09ed89b5b2a3a0a5de060ef9bdd46f750837294b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 643105 (view as bug list) Environment:
Last Closed: 2011-06-28 12:04:10 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: 655403    
Bug Blocks: 643105    
Attachments:
Description Flags
File: backtrace
none
PDF file (shopping list) that has just begin tripping up gs in the print pipeline
none
PPD for HP PhotoSmart 1315
none
ghostscript-gdevcups-segfaults.patch none

Description Charlie Bennett 2010-10-02 12:11:09 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gs -dQUIET -dDEBUG -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOMEDIAATTRS -sDEVICE=cups -sstdout=%stderr -sOUTPUTFILE=%stdout -c '' -f -_
comment:  Attempting to print a PDF generated by OOo Calc.  Will attach.
component: ghostscript
crash_function: cmd_put_list_op
executable: /usr/bin/gs
kernel: 2.6.34.7-56.fc13.x86_64
package: ghostscript-8.71-10.fc13
rating: 4
reason: Process /usr/bin/gs was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1285718610
uid: 4

How to reproduce
-----
1. it happened in the print filter pipeline
2.
3.

Comment 1 Charlie Bennett 2010-10-02 12:11:17 UTC
Created attachment 451188 [details]
File: backtrace

Comment 2 Charlie Bennett 2010-10-02 12:16:39 UTC
Created attachment 451189 [details]
PDF file (shopping list) that has just begin tripping up gs in the print pipeline


I also dropped my ancient HP PhotoSmart 1115 in favor of a slightly less ancient PhotoSmart 1315.  This may have had CUPS bring in GS options not in play before.

Thanks.

Comment 3 Tim Waugh 2010-10-13 15:23:52 UTC
I haven't been able to reproduce this so far.

Please attach the PPD file from the /etc/cups/ppd/ directory, from the queue you were printing to.

Comment 4 Charlie Bennett 2010-10-13 15:35:33 UTC
Created attachment 453238 [details]
PPD for HP PhotoSmart 1315



I also pulled the recent GS updates.  I'm now at ghostscript{,-cups}-8.71-16.fc13.x86_64

Not any better.

Comment 6 Tim Waugh 2010-10-13 16:35:23 UTC
How to reproduce it:

PPD=hp-photosmart-1315.ppd \
gs -dPARANOIDSAFER -sDEVICE=cups -sOUTPUTFILE=/dev/null Shopping08.pdf

Also fails for me here.  Interestingly, ghostscript-9.00 (in rawhide) does not crash -- however, the fact that it only crashes on F-13 when the PPD environment variable is set suggests the bug might be in the gdevcups driver.

Comment 7 Tim Waugh 2010-10-14 15:05:03 UTC
Tried again today with ghostscript-8.71 but using the cups/gdevcups.c from ghostscript-9.00.  This avoids the problem, but I'd like to be able to pinpoint the change that fixes it.

Comment 8 Tim Waugh 2010-10-14 16:07:27 UTC
Created attachment 453506 [details]
ghostscript-gdevcups-segfaults.patch

This subset of the changes fixes it.

Comment 9 Charlie Bennett 2010-10-14 19:06:05 UTC
Grabbed the SRPM off Koji and built it on F13 x86_64 (AMD).

It runs like a top.  Thanks.




The spec file needs a build-depends for libstdc++-devel...

Comment 10 Tim Waugh 2010-10-15 08:58:51 UTC
(In reply to comment #9)
> It runs like a top.  Thanks.

Great.

> The spec file needs a build-depends for libstdc++-devel...

Actually it doesn't:
https://fedoraproject.org/wiki/Packaging:Guidelines#Exceptions_2

libstdc++-devel is brought in by gcc-c++ in that list.

Koji has the built RPMs too...

Comment 11 Charlie Bennett 2010-10-15 11:34:26 UTC
Interesting.  I don't have gcc-c++ installed...

Comment 12 Tim Waugh 2010-10-15 12:00:05 UTC
Please read the link: we don't put things like compilers in BuildRequires tags as it would cause us to have to enumerate the entire build environment in every spec file.  gcc-c++ is part of the "minimal build environment" that is assumed.

Comment 13 Tim Waugh 2010-11-25 17:28:58 UTC
I had to revert this patch due to bug #655403.

Re-opening.

Comment 14 Tim Waugh 2011-05-25 17:31:22 UTC
Also affects Fedora 15 (ghostscript-9.02-1.fc15.x86_64) and upstream (11b5fb5).

Comment 15 Bug Zapper 2011-05-31 12:07:28 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 16 Bug Zapper 2011-06-28 12:04:10 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.