Bug 701922 - [abrt] gnome-panel-2.32.0.2-2.fc14: g_signal_handler_disconnect: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-panel-2.32.0.2-2.fc14: g_signal_handler_disconnect: Process /usr...
Keywords:
Status: CLOSED DUPLICATE of bug 690374
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:48b210b59d2d5f20c29200cbe4f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-04 10:07 UTC by edo
Modified: 2012-03-30 12:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 12:17:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (28.44 KB, text/plain)
2011-05-04 10:08 UTC, edo
no flags Details

Description edo 2011-05-04 10:07:58 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 29118 bytes
cmdline: gnome-panel
component: gnome-panel
Attached file: coredump, 31096832 bytes
crash_function: g_signal_handler_disconnect
executable: /usr/bin/gnome-panel
kernel: 2.6.35.12-90.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: 1304502973
uid: 500

How to reproduce
-----
1.Start PC and Gnome session
2.crash announcement
3.

Comment 1 edo 2011-05-04 10:08:00 UTC
Created attachment 496745 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-30 12:17:46 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 #690377
  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 ***


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