Bug 522981 - [abrt] crash detected in metacity-2.27.1-1.fc12
Summary: [abrt] crash detected in metacity-2.27.1-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 537843
Alias: None
Product: Fedora
Classification: Fedora
Component: metacity
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3869aa61f645769ee6a2933821d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-12 23:25 UTC by Robert Xu
Modified: 2014-06-18 09:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-16 15:09:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (6.46 KB, text/plain)
2009-09-12 23:25 UTC, Robert Xu
no flags Details

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 ***


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