Bug 590930 - [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...
Status: CLOSED DUPLICATE of bug 588039
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb   
(Show other bugs)
Version: 13
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2b4ec3cd7462876fae875f8796b...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-11 01:22 UTC by Gerhard
Modified: 2010-05-25 09:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 09:23:01 UTC
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 (6.86 KB, text/plain)
2010-05-11 01:22 UTC, Gerhard 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Gerhard 2010-05-11 01:22:08 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gthumb
component: gthumb
crash_function: raise
executable: /usr/bin/gthumb
global_uuid: 2b4ec3cd7462876fae875f8796baf31f8e38393e
kernel: 2.6.33.3-85.fc13.i686.PAE
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)
How to reproduce: 1. Just started gthumb.
Comment 1 Gerhard 2010-05-11 01:22:10 UTC 
Created attachment 413013 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:23:01 UTC 

*** This bug has been marked as a duplicate of bug 588039 ***
Comment 3 Karel Klíč 2010-05-25 09:23:01 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #588039.

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