Bug 530693

Summary: [abrt] crash detected in mutter-2.28.0-2.fc12
Product: [Fedora] Fedora Reporter: A S Alam <aalam>
Component: mutterAssignee: Owen Taylor <otaylor>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: findingharrylime, markhuomian, mshao, otaylor, pbrobinson, petersen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:ce661cb63eb84a839a5cc0ed3b72c98b469cf6a8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-08 19:25:18 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 A S Alam 2009-10-24 09:23:30 UTC 
abrt detected a crash.


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


Comment
-----
running command 'gnome-shell -h'

Additional information
======


Attached files
----
backtrace

cmdline
-----
mutter --mutter-plugins=libgnome-shell --replace --sync 


component
-----
mutter


executable
-----
/usr/bin/mutter


kernel
-----
2.6.31.1-56.fc12.x86_64


package
-----
mutter-2.28.0-2.fc12


reason
-----
Process was terminated by signal 11
Comment 1 A S Alam 2009-10-24 09:23:33 UTC 
Created attachment 365927 [details]
File: backtrace
Comment 2 Peter Robinson 2009-10-25 18:57:09 UTC 
Owen can you check this traceback and see if its useful, or close as appropriate.
Comment 3 Peter Robinson 2009-11-08 11:20:10 UTC 
*** Bug 533672 has been marked as a duplicate of this bug. ***
Comment 4 Bug Zapper 2009-11-16 14:10:31 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 5 Peter Robinson 2009-12-15 12:40:40 UTC 
*** Bug 547611 has been marked as a duplicate of this bug. ***
Comment 6 Peter Robinson 2010-01-08 19:25:18 UTC 
fixed upstream.