Bug 649595 - [abrt] gthumb-2.12.0-1.fc13: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
Summary: [abrt] gthumb-2.12.0-1.fc13: Process /usr/bin/gthumb was killed by signal 11 ...
Keywords:
Status: CLOSED DUPLICATE of bug 663172
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb
Version: 13
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bbaa7ab6f3edd5f65fa99877566...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-04 04:41 UTC by BobCat
Modified: 2011-01-27 14:12 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-01-27 14:12:39 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (42.75 KB, text/plain)
2010-11-04 04:41 UTC, BobCat 		no flags Details
View All

Description BobCat 2010-11-04 04:41:03 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: gthumb
component: gthumb
crash_function: comments__read_metadata_ready_cb
executable: /usr/bin/gthumb
kernel: 2.6.34.7-61.fc13.i686.PAE
package: gthumb-2.12.0-1.fc13
rating: 4
reason: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1288845073
uid: 500

comment
-----
I had browsed to the camera file system in gthumb.  It was probably still building the thumbnails
when I closed the program.  There was no evidence of a crash other than ABRT popping up.  No
other system problems apparent.  Was able to launch gthumb with no issues, although I did not
attempt to reproduce crash.  Please write if you want me to provide more info, but be advised 
that I will be formatting the SD card now for reuse.

How to reproduce
-----
1.  Closed gthumb with File->Close
2.
3.
Comment 1 BobCat 2010-11-04 04:41:04 UTC 
Created attachment 457649 [details]
File: backtrace
Comment 2 Michael J. Chudobiak 2011-01-27 14:12:39 UTC 

*** This bug has been marked as a duplicate of bug 663172 ***
Note You need to log in before you can comment on or make changes to this bug.