Bug 669338 - [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 NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:85cbc9ea94a56e9d0fe6bb8b221...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-13 12:15 UTC by bad-luky13
Modified: 2011-03-26 14:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-26 14:24:48 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (60.39 KB, text/plain)
2011-01-13 12:15 UTC, bad-luky13
no flags Details

Description bad-luky13 2011-01-13 12:15:12 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: mutter --mutter-plugins=libgnome-shell
component: mutter
crash_function: st_theme_node_transition_paint
executable: /usr/bin/mutter
kernel: 2.6.35.10-72.fc14.i686
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: 1294878782
uid: 500

How to reproduce
-----
1. Don't know, used gnome-shell
2.
3.

Comment 1 bad-luky13 2011-01-13 12:15:16 UTC
Created attachment 473306 [details]
File: backtrace

Comment 2 Rod Johnson 2011-03-24 21:16:16 UTC
Package: mutter-2.31.5-3.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Login from screen saver


Comment
-----
I don't know if this is reproduceable?

Comment 3 Owen Taylor 2011-03-26 14:24:48 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.