Bug 625744 - [abrt] evince-2.30.3-1.fc13: raise: Process /usr/bin/evince was killed by signal 6 (SIGABRT)
Summary: [abrt] evince-2.30.3-1.fc13: raise: Process /usr/bin/evince was killed by sig...
Alias: None
Product: Fedora
Classification: Fedora
Component: poppler
Version: 14
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:59b336331ae1a3b9f9a1c787c4c...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-20 10:33 UTC by Gerhard
Modified: 2011-07-12 22:02 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2011-07-12 22:02:10 UTC

Attachments (Terms of Use)
File: backtrace (53.27 KB, text/plain)
2010-08-20 10:33 UTC, Gerhard
no flags Details

Description Gerhard 2010-08-20 10:33:50 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evince file:///tmp/epson88v.pdf
component: evince
crash_function: raise
executable: /usr/bin/evince
package: evince-2.30.3-1.fc13
rating: 4
reason: Process /usr/bin/evince was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1282300259
uid: 500

How to reproduce
1. Try to open 'http://www.digimex.at/pub/epson88v.pdf' with firefox -> Crash

Comment 1 Gerhard 2010-08-20 10:33:53 UTC
Created an attachment (id=439901)
File: backtrace

Comment 2 Marek Kašík 2010-11-23 17:20:40 UTC

I've found out that the problem is on the 3721st line of the PDF. There is "574 0 obj<</ShadingType 2/ColorSpace 402 0 R/BBox[-1000000015047466200000000000000 -1000000015047466200000000000000 1000000015047466200000000000000 1000000015047466200000000000000]/Function 810 0 R/Coords[0 0 1 0]/Extend[true true]>>".
Those BBox coordinates are stored as objError types but getNum() expects objInt or objReal types. The abort() is a reaction of poppler to this situation.



Comment 3 Bug Zapper 2011-06-01 11:03:43 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: 

Comment 4 Fedora Update System 2011-06-22 08:52:09 UTC
poppler-0.14.5-3.fc14 has been submitted as an update for Fedora 14.

Comment 5 Fedora Update System 2011-06-24 03:34:33 UTC
Package poppler-0.14.5-3.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing poppler-0.14.5-3.fc14'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2011-07-12 22:01:58 UTC
poppler-0.14.5-3.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.