Bug 681420

Summary: [abrt] gthumb-2.12.2-1.fc14.1: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: sly <slybloty>
Component: gthumbAssignee: Christian Krause <chkr>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: chkr
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:ff472a31ae3b28bc180cb57fb09b2028942130a4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 16:38:20 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 sly 2011-03-02 04:19:24 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 35270 bytes
cmdline: gthumb '/media/Sly D. Iraq 2008-2009/2008-10-06--08.31.04.jpg'
component: gthumb
Attached file: coredump, 63385600 bytes
crash_function: comments__read_metadata_ready_cb
executable: /usr/bin/gthumb
kernel: 2.6.35.9-64.fc14.i686
package: gthumb-2.12.2-1.fc14.1
rating: 4
reason: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: I opened a photo from a cd and gthumb didn't load completely, the list of photos was missing. When I tried to scroll up or down to a different photo it crashed.
time: 1299039335
uid: 500
Comment 1 sly 2011-03-02 04:19:25 UTC 
Created attachment 481781 [details]
File: backtrace
Comment 2 sly 2011-03-07 14:42:28 UTC 
Package: gthumb-2.12.2-1.fc14.1
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
I opened a photo and it crashed right away.
Comment 3 abrt-bot 2012-03-20 16:38:20 UTC 
Backtrace analysis found this bug to be similar to bug #663172, closing as duplicate.

Bugs which were found to be similar to this bug: bug #649595, bug #663172, bug #680711, bug #742787

This comment is automatically generated.

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