Bug 676727

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: Jiri Moskovcak <jmoskovc>
Component: ristrettoAssignee: Christoph Wickert <cwickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: cwickert, dfediuck
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f6eb7a1f1d07d668bf253e5724c4bc3eb30c33ac
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-23 15:54:53 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

Description Jiri Moskovcak 2011-02-10 23:17:52 UTC 
abrt version: 1.2.0
comment: I know the backtrace is incomplete, but it seems to be 100% reproducible so the bad backtrace shouldn't be a big problem. I can try harder and produce a better backtrace manually if needed.
executable: /usr/bin/ristretto
cmdline: ristretto /home/jmoskovc/Desktop/DSC00406.JPG
component: ristretto
uid: 500
Attached file: coredump, 36970496 bytes
kernel: 2.6.35.10-74.fc14.x86_64
crash_function: rstto_thumbnail_get_image
reason: Process /usr/bin/ristretto was killed by signal 11 (SIGSEGV)
package: ristretto-0.0.91-1.fc14
release: Fedora release 14 (Laughlin)
architecture: x86_64
Attached file: backtrace, 9310 bytes
rating: 1
time: 1297379522

How to reproduce
-----
1. open jpg file in ristretto
2. press delete to remove a file
3. confirm you want to really delete the file in the popup dialog
Comment 1 Jiri Moskovcak 2011-02-10 23:17:54 UTC 
Created attachment 478149 [details]
File: backtrace
Comment 2 Christoph Wickert 2011-02-23 15:54:53 UTC 
We have a better backtrace in bug 679808 now.

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