Bug 595293 - [abrt] crash in gnome-panel-2.28.0-16.fc12: raise: Process /usr/libexec/notification-area-applet was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnome-panel-2.28.0-16.fc12: raise: Process /usr/libexec/notif...
Keywords:
Status: CLOSED DUPLICATE of bug 573348
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:985d160c93590eb15031d348385...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-24 10:19 UTC by Daniel Stripes
Modified: 2010-05-25 09:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:23:58 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (45.54 KB, text/plain)
2010-05-24 10:19 UTC, Daniel Stripes 		no flags Details
View All

Description Daniel Stripes 2010-05-24 10:19:48 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_NotificationAreaApplet_Factory --oaf-ior-fd=39
component: gnome-panel
crash_function: raise
executable: /usr/libexec/notification-area-applet
global_uuid: 985d160c93590eb15031d3483857ea7b5ca37116
kernel: 2.6.32.12-115.fc12.x86_64
package: gnome-panel-2.28.0-16.fc12
rating: 4
reason: Process /usr/libexec/notification-area-applet was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 Daniel Stripes 2010-05-24 10:19:50 UTC 
Created attachment 416078 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:23:58 UTC 

*** This bug has been marked as a duplicate of bug 573348 ***
Comment 3 Karel Klíč 2010-05-25 09:23:58 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 #573348.

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