Bug 676944 - [abrt] gnome-panel-2.32.0.2-2.fc14: remove_entry: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-panel-2.32.0.2-2.fc14: remove_entry: Process /usr/bin/gnome-pane...
Keywords:
Status: CLOSED DUPLICATE of bug 677022
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b28a3f6213d775c4e3c5e3a64ca...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-11 23:37 UTC by David
Modified: 2012-03-20 16:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 16:27:31 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (20.91 KB, text/plain)
2011-02-11 23:37 UTC, David
no flags Details

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 ***


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