Bug 706727

Summary: [abrt] evince-2.32.0-4.fc14: memcpy: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Sebastian Krämer <skr>
Component: evinceAssignee: Marek Kašík <mkasik>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: mkasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:79fab4041d053bc7415a168a963a334f8a282f1d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-08 14:33:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
problematic file none

Description Sebastian Krämer 2011-05-22 14:24:12 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 182924 bytes
cmdline: evince /home/sebi/Download/talk-dagm99_4.ps.gz
comment: Reproducible everytime.
component: evince
Attached file: coredump, 59121664 bytes
crash_function: memcpy
executable: /usr/bin/evince
kernel: 2.6.38-0.rc7.git2.3.fc16.x86_64
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)
How to reproduce: Tried to open the ps.gz.
time: 1306073299
uid: 500
Comment 1 Sebastian Krämer 2011-05-22 14:24:16 UTC 
Created attachment 500271 [details]
File: backtrace
Comment 2 Sebastian Krämer 2011-05-22 14:25:26 UTC 
Created attachment 500272 [details]
problematic file
Comment 3 Sebastian Krämer 2011-05-29 06:37:41 UTC 
Error still occuring in F15 (evince-3.0.0-1.fc15).
Comment 4 Sebastian Krämer 2011-05-29 07:07:59 UTC 
(In reply to comment #3)
> Error still occuring in F15 (evince-3.0.0-1.fc15).

.. but obviously with a different stacktrace. Abrtd filed another bug under #708727.
Comment 5 Sebastian Krämer 2011-06-08 14:33:37 UTC 
Probably same error as with evince 3.0 which appears to be fixed now. (Don't have evince 2.32 any more but feel free to reopen if you do and experience issues.)
Comment 6 Sebastian Krämer 2011-06-08 14:36:46 UTC 

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