Bug 627484 - [abrt] evince-2.30.3-1.fc13: repeat: Process /usr/bin/evince was killed by signal 8 (SIGFPE)
Summary: [abrt] evince-2.30.3-1.fc13: repeat: Process /usr/bin/evince was killed by si...
Keywords:
Status: CLOSED DUPLICATE of bug 618346
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9cbb8e86d6332e62bc66708983e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-26 07:23 UTC by Peter H. Jones
Modified: 2010-09-08 07:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-08 07:10:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (137.26 KB, text/plain)
2010-08-26 07:23 UTC, Peter H. Jones
no flags Details

Description Peter H. Jones 2010-08-26 07:23:37 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: evince file:///tmp/LinuxTag%20-%20Customizing%20Fedora.pdf
component: evince
crash_function: repeat
executable: /usr/bin/evince
kernel: 2.6.33.8-149.fc13.i686.PAE
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: 1282806987
uid: 500

How to reproduce
-----
1. Tried to download PDF of Revisor presentation.
2. Didn't try to reproduce.
3.

Comment 1 Peter H. Jones 2010-08-26 07:23:41 UTC
Created an attachment (id=441129)
File: backtrace

Comment 2 Mohamed AMAZIRH 2010-09-03 13:59:23 UTC
Package: evince-2.30.3-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.Download this pdf : https://fedorahosted.org/revisor/attachment/wiki/Presentations/LinuxTag%20-%20Customizing%20Fedora.pdf?format=raw
2.Open it with evince
3.Evince crash

Comment 3 Marek Kašík 2010-09-08 07:10:49 UTC

*** This bug has been marked as a duplicate of bug 618346 ***


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