Bug 605230 - [abrt] crash in gthumb-2.11.3-1.fc13: __strlen_sse2: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gthumb-2.11.3-1.fc13: __strlen_sse2: Process /usr/bin/gthumb ...
Keywords:
Status: CLOSED DUPLICATE of bug 595510
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:43241936751599a0c485ffe2c85...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-17 13:30 UTC by Tadej Janež
Modified: 2010-08-02 22:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-02 22:38:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (58.22 KB, text/plain)
2010-06-17 13:30 UTC, Tadej Janež
no flags Details

Description Tadej Janež 2010-06-17 13:30:18 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gthumb '/home/tadej/Pictures/2010/06-Sloveski evharisti\xc4\x8dni kongres/IMG_0867.JPG'
component: gthumb
crash_function: __strlen_sse2
executable: /usr/bin/gthumb
global_uuid: 43241936751599a0c485ffe2c85154ddcd4de07d
kernel: 2.6.33.5-112.fc13.i686.PAE
package: gthumb-2.11.3-1.fc13
rating: 3
reason: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Open gthumb in a folder also containing MPEG videos.
2. gthumb crashes.
3.

Comment 1 Tadej Janež 2010-06-17 13:30:22 UTC
Created attachment 424815 [details]
File: backtrace

Comment 2 Fedora Admin XMLRPC Client 2010-07-17 22:08:11 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Benjamín Valero Espinosa 2010-08-02 22:38:29 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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


Note You need to log in before you can comment on or make changes to this bug.