Bug 703685 - [abrt] mutter-2.31.5-3.fc14: object_instance_finalize: Process /usr/bin/mutter was killed by signal 6 (SIGABRT)
Summary: [abrt] mutter-2.31.5-3.fc14: object_instance_finalize: Process /usr/bin/mutte...
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:bdc2a44fdd3f99a496f28d1ed92...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-11 01:55 UTC by MLongN
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:53 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (18.52 KB, text/plain)
2011-05-11 01:55 UTC, MLongN
no flags Details

Description MLongN 2011-05-11 01:55:36 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 18969 bytes
cmdline: mutter --mutter-plugins=libgnome-shell
comment: I was just writing a mail with thunderbird (nautilus, rhythmbox, empathy, Transmission and firefox(youtube) was running). Using gnome-shell (don't know if these information can help but I hope so)
component: mutter
Attached file: coredump, 292061184 bytes
crash_function: object_instance_finalize
executable: /usr/bin/mutter
kernel: 2.6.35.12-90.fc14.x86_64
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: 1305077077
uid: 500

How to reproduce
-----
1.Sorry but I don't know how to reproduce it
2.
3.

Comment 1 MLongN 2011-05-11 01:55:40 UTC
Created attachment 498189 [details]
File: backtrace

Comment 2 Owen Taylor 2011-05-25 21:38:53 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.