Bug 666421

Summary: [abrt] evince-2.32.0-2.fc14: __libc_message: Process /usr/bin/evince was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: David Hampton <bugzilla>
Component: evinceAssignee: Marek Kašík <mkasik>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: mkasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c2ab7441b015629f150ee9ac27bb584927495efb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 12:32:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description David Hampton 2010-12-30 16:23:33 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: evince '/home/david/Personal/Finance/2010/David Hampton 2010 Tax Documents/Paystub 2010-12-23.pdf'
comment: This was a transient error. I retried the command and evince started correctly on the same file. 
component: evince
crash_function: __libc_message
executable: /usr/bin/evince
kernel: 2.6.35.9-64.fc14.x86_64
package: evince-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evince was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1293725807
uid: 1001

How to reproduce
-----
1. Start evince on a file
Comment 1 David Hampton 2010-12-30 16:23:35 UTC 
Created attachment 471200 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 12:32:31 UTC 
Backtrace analysis found this bug to be similar to bug #727085, closing as duplicate. This bug seems to belong to component cairo or pixman.

Bugs which were found to be similar to this bug: 
  evince: bug #727085, bug #790296
  gnome-shell: bug #702816

This comment is automatically generated.

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