Bug 690377

Summary: [abrt] gnome-panel-2.32.0.2-2.fc14: g_signal_handler_disconnect: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: edo <edosurina>
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: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:17d1b428d97b6bd30cc7dfd255d1c298db8c4c5a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 12:17:38 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 edo 2011-03-24 05:51:34 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 29810 bytes
cmdline: gnome-panel
comment: NVIDIA with proprietary driver
component: gnome-panel
Attached file: coredump, 32518144 bytes
crash_function: g_signal_handler_disconnect
executable: /usr/bin/gnome-panel
kernel: 2.6.35.11-83.fc14.x86_64
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: 1300944856
uid: 500

How to reproduce
-----
1.start PC+Gnome session
2.start gpk-update+Firefox4
3.crash
Comment 1 edo 2011-03-24 05:51:36 UTC 
Created attachment 487210 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 12:17:38 UTC 
Backtrace analysis found this bug to be similar to bug #690374, closing as duplicate.

Bugs which were found to be similar to this bug: 
  abrt: bug #690373
  gnome-packagekit: bug #690372
  gnome-panel: bug #701922
  gnome-power-manager: bug #690376
  notification-daemon: bug #690374

This comment is automatically generated.

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