Bug 676944

Summary: [abrt] gnome-panel-2.32.0.2-2.fc14: remove_entry: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: David <dmchudzinski>
Component: gnome-panelAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:b28a3f6213d775c4e3c5e3a64ca07a3520765dbf
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 16:27:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description David 2011-02-11 23:37:26 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: gnome-panel
component: gnome-panel
crash_function: remove_entry
executable: /usr/bin/gnome-panel
kernel: 2.6.35.11-83.fc14.i686
package: gnome-panel-2.32.0.2-2.fc14
rating: 4
reason: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297467244
uid: 500

How to reproduce
-----
1.
2.
3.
I was clicking on places on the top menu and this came up.
Comment 1 David 2011-02-11 23:37:29 UTC 
Created attachment 478328 [details]
File: backtrace
Comment 2 David 2011-04-12 21:54:12 UTC 
Package: gnome-panel-2.32.0.2-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
panel crashed while using another program
Comment 3 abrt-bot 2012-03-20 16:27:31 UTC 
Backtrace analysis found this bug to be similar to bug #677022, closing as duplicate. This bug seems to belong to component gtk2, glib2, libcanberra or pulseaudio.

This comment is automatically generated.

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