Bug 721180

Summary: [abrt] evince-2.32.0-4.fc14: remove_range_from_freelist: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: christosp
Component: evinceAssignee: Marek Kašík <mkasik>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: mkasik
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:e705215ec56baa4d302d51d490b04197fdeeb91d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 16:48:22 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 christosp 2011-07-13 23:14:25 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 81872 bytes
cmdline: /usr/bin/evince D1.1.dvi
component: evince
Attached file: coredump, 84557824 bytes
crash_function: remove_range_from_freelist
executable: /usr/bin/evince
kernel: 2.6.35.13-92.fc14.i686
package: evince-2.32.0-4.fc14
rating: 4
reason: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1310598765
uid: 500

How to reproduce
-----
1.I just tried to open a dvi file using evince...
2.
3.
Comment 1 christosp 2011-07-13 23:14:29 UTC 
Created attachment 512767 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 16:48:22 UTC 
Backtrace analysis found this bug to be similar to bug #773309, closing as duplicate.

Bugs which were found to be similar to this bug: bug #601759, bug #607331, bug #629258, bug #636320, bug #640469, bug #642085, bug #649547, bug #657762, bug #666709, bug #667821, bug #669871, bug #698751, bug #706766, bug #717005, bug #733941, bug #773309

This comment is automatically generated.

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