Bug 638531 - [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 598612
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:63becee819d4f8f4e815be5ff81...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-29 09:44 UTC by Cyril FRANCOIS
Modified: 2010-11-09 16:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:07:31 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (35.84 KB, text/plain)
2010-09-29 09:44 UTC, Cyril FRANCOIS 		no flags Details
View All

Description Cyril FRANCOIS 2010-09-29 09:44:49 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: gnome-panel
component: gnome-panel
crash_function: raise
executable: /usr/bin/gnome-panel
kernel: 2.6.34.6-54.fc13.x86_64
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: 1285753363
uid: 500

How to reproduce
-----
1. Use the gnome-applet-globalmenu 0.7.8 with the 'integrate it in the gnome-panel" option
2.Open Gnote to write a note (Gnote 0.7.2) (with the menu application or shortcut in gnome-panel)
3.Suppress the note
4.Confirm we want to suppress the note
Comment 1 Cyril FRANCOIS 2010-09-29 09:44:51 UTC 
Created attachment 450424 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:07:31 UTC 

*** This bug has been marked as a duplicate of bug 598612 ***
Comment 3 Karel Klíč 2010-11-09 16:07:31 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 #598612.

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