Bug 560221 - [abrt] crash in evince-2.28.2-1.fc12
Summary: [abrt] crash in evince-2.28.2-1.fc12
Status: CLOSED DUPLICATE of bug 556810
Alias: None
Product: Fedora
Classification: Fedora
Component: evince   
(Show other bugs)
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:92e445c2cded68ccb175fbb43c5...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-30 13:29 UTC by tuxinator
Modified: 2010-03-24 16:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-03-24 16:56:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (31.36 KB, text/plain)
2010-01-30 13:29 UTC, tuxinator
no flags Details
The broken pdf (1.16 MB, application/pdf)
2010-01-30 13:37 UTC, tuxinator
no flags Details

Description tuxinator 2010-01-30 13:29:29 UTC
abrt 1.0.4 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evince '/home/merten/musik/Noten/The /home/m /h /ho /home/merten/musik/Noten/The Ph'
component: evince
executable: /usr/bin/evince
kernel: 2.6.31.12-174.2.3.fc12.x86_64
package: evince-2.28.2-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)
How to reproduce: 1. Just open the pdf

comment
-----
evince is not able to open this pdf.
The file must have been damaged somehow, because when I open it with okular or adobe reader, it looks broken and is barely readable.

Comment 1 tuxinator 2010-01-30 13:29:34 UTC
Created attachment 387728 [details]
File: backtrace

Comment 2 tuxinator 2010-01-30 13:37:02 UTC
Created attachment 387730 [details]
The broken pdf

Comment 3 Marek Kašík 2010-03-24 16:56:13 UTC

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


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