Bug 619993 - [abrt] crash in mutter-2.29.1-1.fc13: gray_find_cell: Process /usr/bin/mutter was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in mutter-2.29.1-1.fc13: gray_find_cell: Process /usr/bin/mutter...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1a59429b4494f91f9b46207e0c5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-31 08:34 UTC by Allen
Modified: 2011-03-26 14:24 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-26 14:24:55 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (126.21 KB, text/plain)
2010-07-31 08:34 UTC, Allen 		no flags Details
View All

Description Allen 2010-07-31 08:34:50 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: mutter --mutter-plugins=libgnome-shell
component: mutter
crash_function: gray_find_cell
executable: /usr/bin/mutter
global_uuid: 1a59429b4494f91f9b46207e0c5375bf1f15b984
kernel: 2.6.33.6-147.fc13.x86_64
package: mutter-2.29.1-1.fc13
rating: 4
reason: Process /usr/bin/mutter was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. just log in to Gnome Shell
2.
3.
Comment 1 Allen 2010-07-31 08:34:58 UTC 
Created attachment 435739 [details]
File: backtrace
Comment 2 Owen Taylor 2011-03-26 14:24:55 UTC 
I'm closing all bugs filed against Mutter for Fedora 13 and Fedora 14. This represent quite old versions of Mutter and GNOME Shell and are unlikely to have much relevance to the current code base. (The Fedora 14 version of Mutter dates to last June and an enormous amount of development has gone on since that point.)

I'm sorry about not being able to be more attentive to these bugs and crash reports - I know it does take time to file one, and definitely appreciate the effort!
Note You need to log in before you can comment on or make changes to this bug.