Bug 677057

Summary: [abrt] metacity-2.30.3-1.fc14: _XAllocID: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: David <dmchudzinski>
Component: metacityAssignee: Owen Taylor <otaylor>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:3f2c2bef5ffe1c4de9e343012b735f777ca6c924
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 14:37:34 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-13 00:18:04 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: metacity
component: metacity
crash_function: _XAllocID
executable: /usr/bin/metacity
kernel: 2.6.35.11-83.fc14.i686
package: metacity-2.30.3-1.fc14
rating: 4
reason: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297555838
uid: 500

How to reproduce
-----
1.
2.
3.
This issue came up while I was using automatic bug reporting tool.  I was logged out and had to log back in under the user name.

Comment 1 David 2011-02-13 00:18:06 UTC
Created attachment 478415 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-21 14:37:34 UTC
Backtrace analysis found this bug to be similar to bug #699076, closing as duplicate. This bug seems to belong to component gtk2, glib2, cairo, libXrender or libX11.

Bugs which were found to be similar to this bug: 
  emacs: bug #743059
  evolution: bug #710910
  gnome-system-monitor: bug #651239, bug #699061, bug #710654
  gnote: bug #699076
  libX11: bug #708271

This comment is automatically generated.

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