abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: metacity component: metacity crash_function: meta_prefs_get_workspace_name executable: /usr/bin/metacity kernel: 2.6.34.7-63.fc13.x86_64 package: metacity-2.30.0-3.fc13 rating: 4 reason: Process /usr/bin/metacity was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) time: 1291897447 uid: 500 How to reproduce ----- 1. Clicked on Opera Options while download dialog was in the process of opening 2. X-Window froze, had to kill it with Ctrl-Alt-Backspace to return to command line, and restart X. 3.
Created attachment 467731 [details] File: backtrace
Package: metacity-2.30.0-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start X 2. 3.
Package: metacity-2.30.0-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Happens haphazardly. 2. 3.
Package: metacity-2.30.0-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Startx - metacity crashed upon starting X. 2. 3.
Package: metacity-2.30.0-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Don't know. 2. 3.
Package: metacity-2.30.0-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I added 36 workspaces (the maximum) 2. Crash occured, had to reboot. 3. No borders around my dialogs anymore, everything looks really weird
Package: metacity-2.30.0-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Was working on Skype messenger suddenly the system started misbehaving. Skype was accepting typed characters randomly, some being entered, others not. The cursor was permanently in text edit mode no matter where it is moved on screen, desktop was not responding to any actions. Had to bail out with Ctrl-Alt-Backspace to recover. 2. 3.
Package: metacity-2.30.0-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. System was unattended, so I really do not know the circumstances. 2. 3.
Package: metacity-2.30.0-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Hppens erratically. Can't determine exact circumstances. 2. 3.
Package: metacity-2.30.0-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Do not know. 2. 3.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed.