Bug 658875

Summary: [abrt] gnome-terminal-2.32.0-1.fc14: gtk_gc_key_hash: Process /usr/bin/gnome-terminal was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Ferry Huberts <mailings>
Component: gnome-terminalAssignee: Behdad Esfahbod <behdad>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: behdad
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:cd5dcde8520a515dcd4db0c46b99332cc2d75702
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 12:21:53 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
File: backtrace none

Description Ferry Huberts 2010-12-01 09:50:47 EST
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: gnome-terminal --geometry 140x40
component: gnome-terminal
crash_function: gtk_gc_key_hash
executable: /usr/bin/gnome-terminal
kernel: 2.6.35.6-48.fc14.x86_64
package: gnome-terminal-2.32.0-1.fc14
rating: 4
reason: Process /usr/bin/gnome-terminal was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1291214747
uid: 500

How to reproduce
-----
1. right after compiz crashed (see #657943)
2.
3.
Comment 1 Ferry Huberts 2010-12-01 09:50:51 EST
Created attachment 463991 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 12:21:53 EDT
Backtrace analysis found this bug to be similar to bug #664254, closing as duplicate. This bug seems to belong to component gtk2 or glib2.

Bugs which were found to be similar to this bug: 
  NetworkManager: bug #648767
  blueman: bug #552042, bug #556498
  gnome-media: bug #648765
  gnome-power-manager: bug #554346, bug #648768
  nautilus: bug #664254
  pidgin: bug #610291

This comment is automatically generated.

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