Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 586964

Summary: [abrt] crash in evince-2.30.1-1.fc13: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: atdiehm
Component: evinceAssignee: Marek Kašík <mkasik>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: mkasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:42b5f7f832940f0171897dc086a09d31016a1375
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-28 15:32:18 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 atdiehm 2010-04-28 15:07:32 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evince /home/atdiehm/Desktop/TRT_Files/Contracts/Quotes/AD/Chelian-AD120409.pdf
component: evince
executable: /usr/bin/evince
global_uuid: 42b5f7f832940f0171897dc086a09d31016a1375
kernel: 2.6.33.2-57.fc13.x86_64
package: evince-2.30.1-1.fc13
rating: 4
reason: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 atdiehm 2010-04-28 15:07:34 UTC 
Created attachment 409875 [details]
File: backtrace
Comment 2 atdiehm 2010-04-28 15:09:52 UTC 
I was opening a PDF on a mounted NFS share.  It crashes every time.  This is a pretty vanilla install of F13b, only 1 day old.
Comment 3 Marek Kašík 2010-04-28 15:32:18 UTC 

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