Bug 592661 - [abrt] crash in gthumb-2.11.3-1.fc13: raise: Process /usr/bin/gthumb was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gthumb-2.11.3-1.fc13: raise: Process /usr/bin/gthumb was kill...
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:6dee76beeb1cce8d287e29c2604...
: 592662 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-16 01:45 UTC by Martin Ebourne
Modified: 2010-06-08 13:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-08 13:03:42 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (60.05 KB, text/plain)
2010-05-16 01:45 UTC, Martin Ebourne
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 620966 None None None Never

Description Martin Ebourne 2010-05-16 01:45:48 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gthumb
comment: Just displaying a folder including comments created with an older gthumb.
component: gthumb
crash_function: raise
executable: /usr/bin/gthumb
global_uuid: 6dee76beeb1cce8d287e29c26041609f7f10a6cf
package: gthumb-2.11.3-1.fc13
rating: 4
reason: Process /usr/bin/gthumb was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

Comment 1 Martin Ebourne 2010-05-16 01:45:50 UTC
Created attachment 414307 [details]
File: backtrace

Comment 2 Martin Ebourne 2010-05-16 01:50:56 UTC
*** Bug 592662 has been marked as a duplicate of this bug. ***

Comment 3 Martin Ebourne 2010-05-16 01:52:34 UTC
Both of these are malloc errors destructing ExivDatum.

Comment 4 Michael J. Chudobiak 2010-06-08 13:03:57 UTC

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