Red Hat Bugzilla – Bug 596747
Assertion failure in meta_prefs_get_workspace_name()
Last modified: 2011-06-27 12:48:14 EDT
abrt 1.1.0 detected a crash.
Attached file: backtrace
reason: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
I manage a bunch of servers and I configured my display with 24 workspaces, one for every server. Usually with previous versions of Fedora (12 and before) there were no problems using that many workspaces. I tried with 6, 12, 15 and 18 workspaces. At 18 and over, metacity starts crashing.
How to reproduce
1. Increate the number of workspaces beyong 15
Created attachment 417226 [details]
*** Bug 596754 has been marked as a duplicate of this bug. ***
*** Bug 603561 has been marked as a duplicate of this bug. ***
*** Bug 585724 has been marked as a duplicate of this bug. ***
*** Bug 595020 has been marked as a duplicate of this bug. ***
*** Bug 615400 has been marked as a duplicate of this bug. ***
How to reproduce
1. gconftool-2 -s --type int /apps/metacity/general/num_workspaces 20
2. CTRL+Alt+CURSOR-RIGHT at least once
I have this too.
I routinely have 21 workspaces on Fedora 12.
After a new installation with Fedora 14 (but retaining the old /home) I got this problem. I had to use the gconftool-2 illustrated in this bug report to change it to 15 to stop the respeated crash.
I encountered this issue also on Fedora 14.
I use Red Hat and Fedora for years through RHEL 5 & Fedora 10 with GNOME Desktop Sessions that have at least 18 to 24 Workspaces. I manage several RHEL Systems in Data Centers around the World. Hence, I have become extremely dependent on using several Workspaces.
I would like to get a solution to this soon. If there is anything I can do to assist, then please let me know. I have a lot of Programming Experience.
I use gconf-editor and fill up the name_XX entries up to 24 by hand in:
IIRC one can run gconf-editor without a window manager.
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:
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.