Bug 756059 - [abrt] evince-2.28.2-2.fc12: memcpy: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
Summary: [abrt] evince-2.28.2-2.fc12: memcpy: Process /usr/bin/evince was killed by si...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 12
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4d8f2803a88fe2731ab2d0ab6c6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-22 15:52 UTC by Alex
Modified: 2016-02-10 14:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-26 09:28:18 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (64.25 KB, text/plain)
2011-11-22 15:52 UTC, Alex 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Alex 2011-11-22 15:52:23 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evince /home/akoufos/lapw/Fr/Plots/FrlapwldaENTHALPY.eps
comment: Going from 200% to 150% to 100% works fine, although slow and seems like it might crash.
component: evince
crash_function: memcpy
executable: /usr/bin/evince
kernel: 2.6.32.26-175.fc12.x86_64
package: evince-2.28.2-2.fc12
rating: 4
reason: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
time: 1321976682
uid: 500

How to reproduce
-----
1. Started in full screen with 200% view
2. Went from 200% view to 100% in full screen
3. Crashed before seeing the 100% view
Comment 1 Alex 2011-11-22 15:52:26 UTC 
Created attachment 535084 [details]
File: backtrace
Comment 2 Jan Kurik 2015-12-22 11:34:23 UTC 
This bug is currently assigned to an unsupported release. If you think this bug is still valid and should remain open, please re-assign it to a supported release (F22, F23) or to rawhide.

Bugs which will be assigned to an unsupported release are going to be closed as EOL (End Of Life) on January 26th, 2016.
Note You need to log in before you can comment on or make changes to this bug.