Bug 693794

Summary: [abrt] ristretto-0.0.91-1.fc14: rstto_thumbnail_get_image: Process /usr/bin/ristretto was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: rdesfo
Component: ristrettoAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:69354bc50afc547a3c7f5d6e99b6b8cf68f8fd7c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-05 16:33:33 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 rdesfo 2011-04-05 15:26:47 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 9833 bytes
cmdline: ristretto /home/ryan/Downloads/n900/20110330_006.jpg /home/ryan/Downloads/n900/20110330_005.jpg /home/ryan/Downloads/n900/20110330_004.jpg /home/ryan/Downloads/n900/20110330_003.jpg /home/ryan/Downloads/n900/20110330_002.jpg /home/ryan/Downloads/n900/20110330_001.jpg
component: ristretto
Attached file: coredump, 101122048 bytes
crash_function: rstto_thumbnail_get_image
executable: /usr/bin/ristretto
kernel: 2.6.35.11-83.fc14.i686
package: ristretto-0.0.91-1.fc14
rating: 4
reason: Process /usr/bin/ristretto was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302017070
uid: 500

How to reproduce
-----
1. open ristretto
2. copied image
3. closed image and then the image viewer crashed
Comment 1 rdesfo 2011-04-05 15:26:49 UTC 
Created attachment 490013 [details]
File: backtrace
Comment 2 Christoph Wickert 2011-04-05 16:33:33 UTC 
This is fixed in ristretto 0.0.93, however this version cannot be built in Fedora 14, I'm sorry.

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