Bug 651256 - [abrt] gnome-panel-2.32.0.2-2.fc14: Process /usr/libexec/notification-area-applet was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-panel-2.32.0.2-2.fc14: Process /usr/libexec/notification-area-ap...
Keywords:
Status: CLOSED DUPLICATE of bug 651255
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:739a2d6eccf32a0e65dd0479548...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-09 04:53 UTC by Michael Cronenworth
Modified: 2012-03-21 14:49 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-21 14:49:18 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (38.85 KB, text/plain)
2010-11-09 04:53 UTC, Michael Cronenworth 		no flags Details
View All

Description Michael Cronenworth 2010-11-09 04:53:54 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/notification-area-applet
component: gnome-panel
executable: /usr/libexec/notification-area-applet
kernel: 2.6.35.6-48.fc14.x86_64
package: gnome-panel-2.32.0.2-2.fc14
reason: Process /usr/libexec/notification-area-applet was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1289276553
uid: 502

comment
-----
I have a locally authenticated system with only one gnome panel bar. This system was upgraded from F13 to F14 using preupgrade.

How to reproduce
-----
1.  Logged into gnome session.
2.
3.
Comment 1 Michael Cronenworth 2010-11-09 04:53:57 UTC 
Created attachment 458971 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 14:49:18 UTC 
Backtrace analysis found this bug to be similar to bug #651255, closing as duplicate.

Bugs which were found to be similar to this bug: bug #651255, bug #722242

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 651255 ***
Note You need to log in before you can comment on or make changes to this bug.