abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: evince /home/james/Downloads/KongClimbing_Chinese+Russian.pdf component: evince crash_function: repeat executable: /usr/bin/evince kernel: 2.6.34.6-54.fc13.x86_64 package: evince-2.30.3-1.fc13 rating: 4 reason: Process /usr/bin/evince was killed by signal 8 (SIGFPE) release: Fedora release 13 (Goddard) time: 1284554677 uid: 500 How to reproduce ----- 1. 2. 3. scolling through the document
Created an attachment (id=447472) File: backtrace
Package: evince-2.30.3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Opening a file via web browser (MS outlook webapp in Firefox+mono). 2. Evince crashed immediately without opeing a window. 3. I was in a hurry so just used adobe viewer (also installed on this box) to open the file instead. Comment ----- It appears to be the specific PDF file that causes this, I can open other pdf's out of the outlook webap OK, however, saving this particular file to disk and the re-opening with evince also produces an immediate crash. File was created by Excel2010 PDF writer (according to the PDF info tags). Afraid I cant send a copy of the file, even under NDA, sorry. Hopefully backtrace gives enough.
*** Bug 644423 has been marked as a duplicate of this bug. ***
*** Bug 662406 has been marked as a duplicate of this bug. ***
*** Bug 670076 has been marked as a duplicate of this bug. ***
Package: evince-2.30.3-2.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.a 2. 3. Comment ----- aaaaaaaaaaaaaaa
Package: evince-2.30.3-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Tried to Open PDF with Evince 2. 3.
Package: evince-2.30.3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. download the PDF via https 2. open the PDF automatically with the default application (evince) when the download completes 3. boom Comment ----- xpdf can open it properly
Package: evince-2.30.3-2.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. pulled up the pdf of a W3C conference paper 2. evince blew up 3. Comment ----- Acrobat could handle it. Raw paper available upon request ... after the workshop paper set is published (which will be presently). The URL likely for this is http://www.w3.org/2011/identity-ws/papers.html (i.e. not yet)
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
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.