Bug 599333 - [abrt] crash in evince-2.30.1-2.fc13: ev_metadata_get_string: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evince-2.30.1-2.fc13: ev_metadata_get_string: Process /usr/bi...
Status: CLOSED DUPLICATE of bug 597777
Alias: None
Product: Fedora
Classification: Fedora
Component: evince (Show other bugs)
(Show other bugs)
Version: 13
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:675613b9c5fac998fd4bf5cf926...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-03 07:14 UTC by Alec Leamas
Modified: 2010-06-22 10:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-22 10:02:35 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 (9.60 KB, text/plain)
2010-06-03 07:14 UTC, Alec Leamas
no flags Details

Description Alec Leamas 2010-06-03 07:14:37 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/evince /tmp/mamma.pdf
comment: The attachment is somewhat personal, but is not causing trouble in other viewers. Nor did it crash before I upgraded to F13
component: evince
crash_function: ev_metadata_get_string
executable: /usr/bin/evince
global_uuid: 675613b9c5fac998fd4bf5cf926a0327aab7d5a9
kernel: 2.6.33.5-112.fc13.i686
package: evince-2.30.1-2.fc13
rating: 4
reason: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Opened a pdf attachment  in thunderbird
2.
3.

Comment 1 Alec Leamas 2010-06-03 07:14:39 UTC
Created attachment 419261 [details]
File: backtrace

Comment 2 Marek Kašík 2010-06-22 10:02:35 UTC

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


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