Hide Forgot
abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: evince /home/mario/Desktop/Nessus_Scan_Report.pdf component: evince executable: /usr/bin/evince kernel: 2.6.35.11-83.fc14.x86_64 package: evince-2.32.0-3.fc14 reason: Process /usr/bin/evince was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1297943356 uid: 500 How to reproduce ----- 1. PDF generated from cups-pdf 2. Open with evince PDF 3. Evince crashed
Created attachment 479313 [details] File: backtrace
Hi, Noticed that this issue is true when cups-pdf is used by firefox (firefox-3.6.13-1.fc14.x86_64) (see Fedora_Project_-_Start_Page.pdf attach). When cups-pdf is used by chromium (chromium-10.0.634.0-1.fc14.x86_64) there is no issue here (see _org_chromium_qlptOk.pdf attach).
Created attachment 479348 [details] Firefox print
Created attachment 479349 [details] Chromium print
Package: evince-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. noting 2. 3. Comment ----- tier3 is mounted via sshfs
Package: evince-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Opened older .dvi file 2. Went through several pages 3. Evince crashed Comment ----- I can provide the file, if it helps.
Package: evince-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. on startup 2. no user action 3. Comment ----- attempted to read a pdf file on my Desktop
Package: evince-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Printing to pdf by Print dialog 2. 3.
Package: evince-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Printing PDF document (scanned book, 320 p.) 2. Printing aborted. 3. Crash.
According to the backtrace, you use unsupported versions of freetype and cairo (freetype-infinality and cairo-freeworld). I'm closing this then. Regards Marek
Created attachment 479986 [details] backtrace
This may be true for the original reporter but not in my case. (See the backtrace file in the previous comment.) ABRT identified my crash as a duplicate of the original bug, but I can open new one if you prefer.