abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: mutter --mutter-plugins=libgnome-shell component: mutter executable: /usr/bin/mutter kernel: 2.6.36.1-11.fc15.x86_64 package: mutter-2.91.3-2.fc15 reason: Process /usr/bin/mutter was killed by signal 11 (SIGSEGV) release: Fedora release 15 (Rawhide) time: 1291829921 uid: 500 How to reproduce ----- 1.I don't know 2. 3.
Created attachment 467535 [details] File: backtrace
Package: mutter-2.91.3-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. 2. 3. Crash happened when I moved the pointer to the hot corner in gnome-shell for the first time
Package: mutter-2.91.3-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.just running gnome-shell is apparently enough 2. 3.
Package: mutter-2.91.3-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.? 2. 3.
Package: mutter-2.91.3-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.don't know 2. 3.
Package: mutter-2.91.3-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.started the shell Comment ----- gtk2-2.23.2-1.fc15.x86_64 gtk3-2.91.5-1.fc15.x86_64 clutter-1.5.10-1.fc15.x86_64 mutter-2.91.3-2.fc15.x86_64 gobject-introspection-0.9.12-1.fc15.x86_64 gjs-0.7.7-3.fc15.x86_64 xulrunner-2.0-0.13b8.fc15.x86_64
Created attachment 471763 [details] better backtrace, with some debuginfos installed Program terminated with signal 11, Segmentation fault. #0 GetFinalizableTraceKind (thingKind=4294967295) at jsgc.h:499 499 return map[thingKind];
Package: mutter-2.91.3-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Login to Fedora Rawhide 2. Autostart Empathy 3. After the first notification in the message tray - mutter is crashing Comment ----- mutter is crashing all the time, when there is an action in the message tray, like a chat, gwibber notification, update notification etc. - i'm using ati graphic-card and the ati open source driver.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.