Bug 530693 - [abrt] crash detected in mutter-2.28.0-2.fc12
Summary: [abrt] crash detected in mutter-2.28.0-2.fc12
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ce661cb63eb84a839a5cc0ed3b7...
: 533672 547611 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-24 09:23 UTC by A S Alam
Modified: 2013-07-03 00:56 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-01-08 19:25:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.04 KB, text/plain)
2009-10-24 09:23 UTC, A S Alam
no flags Details

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.


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