After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 625781 - metacity crashes with more than 16 virtual desktops
metacity crashes with more than 16 virtual desktops
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
2.30.x
Other Linux
: Normal critical
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
: 626832 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-08-01 21:58 UTC by Quentin Sculo
Modified: 2011-01-15 22:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Initialise all workspace names (1.31 KB, patch)
2010-08-03 12:37 UTC, Thomas Thurman
none Details | Review

Description Quentin Sculo 2010-08-01 21:58:53 UTC
When using more than 16 virtual desktops, metacity crashes with error :
metacity:ERROR:core/prefs.c:2482:meta_prefs_get_workspace_name: assertion failed: (workspace_names[i] != NULL)
It seems to be because src/metacity.schemas.in.in only defines keys in /apps/metacity/workspace_names/ for desktop 1-16, increasing this to 36 (the maximum metacity lets you have) fixes the problem.

It didn't used to do that even though the obvious related changes in src/metacity.schemas.in.in and in core/prefs.c dates back to 2002, so I don't know what caused this change.
It happened to me after upgrading to mandriva 2010.1 and someone reported it for ubuntu : https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/583847

And before you ask, yes having more than 16 desktops is very useful. I use 24 desktops arranged in 3 columns with a really big workspace switcher, and no taskbar. It's IMHO the best way to manage a desktop, especially with a wide screen.
Comment 1 stlevo 2010-08-02 19:01:03 UTC
The other thing is, that when you change number of workspaces ... metacity works as expected, until restart ... then it refuses to start with no error or indication of any kind. You have to run "metacity --replace" from terminal to get error which is not quite obvious.
Comment 2 bugzilla-gnome 2010-08-02 22:33:16 UTC
  I can confirm this bug on Fedora 13 and Ubuntu 10.04. In my case the error was the one below.

metacity:ERROR:core/prefs.c:2495:meta_prefs_get_workspace_name: assertion failed: (workspace_names[i] != NULL)


Releases:
metacity-2.30.1-0ubuntu1
metacity-2.30.0-3.fc13.x86_64
Comment 3 Thomas Thurman 2010-08-03 12:25:26 UTC
Confirmed.  How annoying.
Comment 4 Thomas Thurman 2010-08-03 12:37:54 UTC
Created attachment 167041 [details] [review]
Initialise all workspace names

Well, I have no idea what changed (in fact, nothing changed as far as I can see, so why it should break is beyond me), but the attached patch fixes the crash.  If anyone would like to look it over, I'd be grateful; I'll commit it in a day or so unless there are objections.
Comment 5 bugzilla-gnome 2010-08-05 15:56:02 UTC
I can confirm that the patch resolves the issue for me on Fedora 13 x86_64 when added to metacity-2.30.0-3.fc13.x86_64.
Comment 6 stlevo 2010-08-06 18:09:18 UTC
you should probably update the schema definition too (as described in the link in first post)
Comment 7 Federico Mena Quintero 2010-09-09 20:00:50 UTC
Go go go!  I get this bug too in openSUSE 11.3 and it is super-annoying.
Comment 8 Danilo Segan 2010-09-23 08:31:31 UTC
*** Bug 626832 has been marked as a duplicate of this bug. ***
Comment 9 Thomas Thurman 2011-01-15 22:54:39 UTC
(In reply to comment #6)
> you should probably update the schema definition too (as described in the link
> in first post)

Good point.  Done.

Committed to master now:
http://git.gnome.org/browse/metacity/commit/?id=04d5891337bb09f64e51d4be5f5c48b2ea60c547

-> FIXED.