Bug 700193 - [abrt] mutter-2.31.5-3.fc14: Process /usr/bin/mutter was killed by signal 11 (SIGSEGV)
Summary: [abrt] mutter-2.31.5-3.fc14: Process /usr/bin/mutter was killed by signal 11 ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c7cea229f16b18846da18551e53...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-27 17:41 UTC by Lari Tanase
Modified: 2011-05-25 21:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-25 21:38:52 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (34.10 KB, text/plain)
2011-04-27 17:41 UTC, Lari Tanase 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Lari Tanase 2011-04-27 17:41:22 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 34923 bytes
cmdline: mutter --mutter-plugins=libgnome-shell
component: mutter
Attached file: coredump, 27193344 bytes
crash_function: shell_global_grab_dbus_service
executable: /usr/bin/mutter
kernel: 2.6.35.12-88.fc14.x86_64
package: mutter-2.31.5-3.fc14
rating: 4
reason: Process /usr/bin/mutter was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1303388188
uid: 500

How to reproduce
-----
1. tried to switch to new gnome3 interface - creashed and recovered only after several hours of workaround in console
2.
3.
Comment 1 Lari Tanase 2011-04-27 17:41:25 UTC 
Created attachment 495299 [details]
File: backtrace
Comment 2 Owen Taylor 2011-05-25 21:38:52 UTC 
Now that Fedora 15 is released, I'm closing all Mutter bugs from Fedora 14, which has a version of Mutter from roughly a year ago; enough is changed that bugs filed against the Fedora 14 version of Mutter are unlikely to be relevant at this point. (The WORKSFORME resolution shouldn't be taken to mean that I've tested the particular hardware configuration or reported reproduction instructions.)
Note You need to log in before you can comment on or make changes to this bug.