Bug 696022 - [abrt] mutter-2.31.5-3.fc14: __libc_message: Process /usr/bin/mutter was killed by signal 6 (SIGABRT)
Summary: [abrt] mutter-2.31.5-3.fc14: __libc_message: Process /usr/bin/mutter was kill...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:440ca43eb951108be14800af1d2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-13 05:33 UTC by Osvaldo Calles
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:49 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (69.23 KB, text/plain)
2011-04-13 05:33 UTC, Osvaldo Calles 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Osvaldo Calles 2011-04-13 05:33:28 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 70891 bytes
cmdline: mutter --mutter-plugins=libgnome-shell
component: mutter
Attached file: coredump, 143204352 bytes
crash_function: __libc_message
executable: /usr/bin/mutter
kernel: 2.6.35.11-83.fc14.i686.PAE
package: mutter-2.31.5-3.fc14
rating: 4
reason: Process /usr/bin/mutter was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1302101699
uid: 500

How to reproduce
-----
1.
2. .
3.
Comment 1 Osvaldo Calles 2011-04-13 05:33:38 UTC 
Created attachment 491638 [details]
File: backtrace
Comment 2 Owen Taylor 2011-05-25 21:38:49 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.