Bug 522981

Summary: [abrt] crash detected in metacity-2.27.1-1.fc12
Product: [Fedora] Fedora Reporter: Robert Xu <robxu9>
Component: metacityAssignee: Søren Sandmann Pedersen <sandmann>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: kem, otaylor, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:3869aa61f645769ee6a2933821df18083e57532a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-16 15:09:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Robert Xu 2009-09-12 23:25:34 UTC 
abrt detected a crash.


How to reproduce
-----
1.
2.
3.


Comment
-----
I have no idea what happened here. Metacity just... crashed. Didn't do anything.

Additional information
======


Attached files
----
backtrace

cmdline
-----
metacity 


component
-----
metacity


executable
-----
/usr/bin/metacity


kernel
-----
2.6.31-2.fc12.i686.PAE


package
-----
metacity-2.27.1-1.fc12


reason
-----
Process was terminated by signal 6
Comment 1 Robert Xu 2009-09-12 23:25:38 UTC 
Created attachment 360824 [details]
File: backtrace
Comment 2 Bug Zapper 2009-11-16 12:19:33 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 Owen Taylor 2009-11-16 15:09:14 UTC 
Some combination of bug 537843 and 537845; it's hard to decipher from the backtrace which is missing some of the necessary debug symbols.

(Most likely the original problem here is that your X server crashed triggering this problem - the backtrace is from Metacity not cleaning up properly when the X server exite.)

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