Bug 600434

Summary: [abrt] crash in gthumb-2.11.3-1.fc13: __strlen_sse2: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Pete Gale <pkgale>
Component: gthumbAssignee: Behdad Esfahbod <behdad>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: behdad, mjc, ogladso
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:5ab4fa24d3c8e3de2712cc6357dcdde8518b21bb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-08 12:31:51 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 Pete Gale 2010-06-04 17:20:48 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gthumb --import-photos /home/pkgale/.gvfs/Gurthang
component: gthumb
crash_function: __strlen_sse2
executable: /usr/bin/gthumb
global_uuid: 5ab4fa24d3c8e3de2712cc6357dcdde8518b21bb
kernel: 2.6.33.5-112.fc13.x86_64
package: gthumb-2.11.3-1.fc13
rating: 4
reason: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Plug in your iPhone
2.
3.

Comment 1 Pete Gale 2010-06-04 17:20:50 UTC
Created attachment 421303 [details]
File: backtrace

Comment 2 Michael J. Chudobiak 2010-06-08 12:31:51 UTC
This has been fixed upstream, and should appear in the gThumb 2.11.4 release.

- Mike

Comment 3 Michael J. Chudobiak 2010-06-08 12:33:05 UTC
*** Bug 600368 has been marked as a duplicate of this bug. ***

Comment 4 Michael J. Chudobiak 2010-06-08 12:33:37 UTC
*** Bug 600367 has been marked as a duplicate of this bug. ***

Comment 5 Michael J. Chudobiak 2010-06-08 12:37:46 UTC
Sorry for the noise, the above two are not duplicates of this bug.