Bug 600367 - [abrt] crash in gthumb-2.11.3-1.fc13: __strlen_sse2: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
[abrt] crash in gthumb-2.11.3-1.fc13: __strlen_sse2: Process /usr/bin/gthumb ...
Status: CLOSED DUPLICATE of bug 595510
Product: Fedora
Classification: Fedora
Component: gthumb (Show other bugs)
13
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Behdad Esfahbod
Fedora Extras Quality Assurance
abrt_hash:8506acdd0b3662482e84cfc970f...
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-04 11:04 EDT by ogladso
Modified: 2010-06-08 08:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-08 08:40:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (79.90 KB, text/plain)
2010-06-04 11:04 EDT, ogladso
no flags Details

  None (edit)
Description ogladso 2010-06-04 11:04:46 EDT
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gthumb '/home/olle/Images and video/Matthew and Andrea/img_0029.jpg'
comment: Open a folder, look at pictures. There is one .avi file in the folder. I was copying other files to a flash drive at the same time.
component: gthumb
crash_function: __strlen_sse2
executable: /usr/bin/gthumb
global_uuid: 8506acdd0b3662482e84cfc970f00124bbb18bef
kernel: 2.6.33.5-112.fc13.i686
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.Look at pictures.
2.
3.
Comment 1 ogladso 2010-06-04 11:04:48 EDT
Created attachment 421252 [details]
File: backtrace
Comment 2 Michael J. Chudobiak 2010-06-08 08:33:37 EDT

*** This bug has been marked as a duplicate of bug 600434 ***
Comment 3 Michael J. Chudobiak 2010-06-08 08:40:28 EDT

*** 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.