Bug 654555 - [abrt] mutter-2.31.5-3.fc14: meta_bug: Process /usr/bin/mutter was killed by signal 6 (SIGABRT)
Summary: [abrt] mutter-2.31.5-3.fc14: meta_bug: Process /usr/bin/mutter was killed by ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c4095202f8ce59e0f63bfaad72b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-18 08:45 UTC by Kvikende
Modified: 2011-03-26 14:26 UTC (History)
4 users (show)

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

Attachments (Terms of Use)
File: backtrace (16.57 KB, text/plain)
2010-11-18 08:45 UTC, Kvikende 		no flags Details
View All

Description Kvikende 2010-11-18 08:45:42 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: mutter --mutter-plugins=libgnome-shell
comment: I am not sure what I do but every time I boot the machine abrt whines about this crash.
component: mutter
crash_function: meta_bug
executable: /usr/bin/mutter
kernel: 2.6.35.6-48.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: 1290018354
uid: 500
Comment 1 Kvikende 2010-11-18 08:45:45 UTC 
Created attachment 461241 [details]
File: backtrace
Comment 2 Owen Taylor 2011-03-26 14:26:31 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.