Bug 639494 - [abrt] gnome-panel-2.30.0-4.fc13: raise: Process /usr/bin/gnome-panel was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-panel-2.30.0-4.fc13: raise: Process /usr/bin/gnome-panel was kil...
Keywords:
Status: CLOSED DUPLICATE of bug 597281
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ca12ee5f11e0aee14178aeb391d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-01 22:04 UTC by Ralph Clark
Modified: 2010-11-09 12:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 12:48:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (26.35 KB, text/plain)
2010-10-01 22:04 UTC, Ralph Clark
no flags Details

Description Ralph Clark 2010-10-01 22:04:06 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: gnome-panel
component: gnome-panel
crash_function: raise
executable: /usr/bin/gnome-panel
kernel: 2.6.34.7-56.fc13.i686.PAE
package: gnome-panel-2.30.0-4.fc13
rating: 4
reason: Process /usr/bin/gnome-panel was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1285946522
uid: 500

Comment 1 Ralph Clark 2010-10-01 22:04:08 UTC
Created attachment 451133 [details]
File: backtrace

Comment 2 Ralph Clark 2010-11-09 10:17:16 UTC
Package: gnome-panel-2.30.0-4.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. File bug report to bugzilla using the Automatic Bug Reporting Tool
2. Press Close Button on the final screen of the Automatic Bug Reporting Tool
3. It crashes and generates another alert in ABRT.

Comment 3 Karel Klíč 2010-11-09 12:48:38 UTC

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

Comment 4 Karel Klíč 2010-11-09 12:48:38 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 #597281.

Sorry for the inconvenience.


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