Ubuntu
metacity package

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

Bug #583847 reported by jalitr on 2010-05-21

This bug affects 13 people

Affects		Status	Importance	Assigned to	Milestone
	Metacity	Fix Released	Critical	gnome-bugs #625781
	metacity (Ubuntu)	Fix Released	Medium	Chris Coulson

Bug Description

Binary package hint: metacity

When upgrading to metacity-1.2.30.1-0ubuntu1, the new package installs without error but metacity does not run when you start X because it cannot find workspace names using gconf. To trigger this bug, create more than 16 workspaces before upgrading. The problem is that the metacity schema in /usr/share/gconf/schemas/metacity.schemas only has slots for 16 workspace names, but metacity lets you have up to 36 workspaces. The workaround is to manually edit the metacity.schemas file and add slots 17 - 36 under the key for /schemas/apps/metacity/workspace_names/name then run "gconf-schemas --register-all".

Tags:

Related branches

lp:ubuntu/natty/metacity

Revision history for this message

Matej Svetlík (matej-svetlik) wrote on 2010-07-19:

this also happens in clean install ...
1) add workspace switcher
2) add e.g. 20 workspaces - everything works like expected
3) restart
4) no metacity after login (no error message or something; just windows without borders)
5) "metacity --replace" gives same error as above

tags:

added: metacity

Bug Watch Updater (bug-watch-updater) on 2010-08-01

Changed in metacity:
status:	Unknown → New

Bug Watch Updater (bug-watch-updater) on 2010-08-03

Changed in metacity:
status:	New → In Progress

Pedro Villavicencio (pedro) on 2010-08-18

Changed in metacity (Ubuntu):
importance:	Undecided → Medium
status:	New → Triaged

Bug Watch Updater (bug-watch-updater) on 2010-09-09

Changed in metacity:
importance:	Unknown → Critical

Bug Watch Updater (bug-watch-updater) on 2011-01-16

Changed in metacity:
status:	In Progress → Fix Released

Revision history for this message

JanBrinkmann (jbrinkmann) wrote on 2011-03-05:

This one is still true for 10.10 amd64 . I just borked my workstation by adding "too much" workspaces (20).

Revision history for this message

JanBrinkmann (jbrinkmann) wrote on 2011-03-06:

metacity_2.30.3-0ubuntu5.debdiff Edit (2.3 KiB, text/plain)

Hi. Since this quite annoying bug was fixed upstream I decided to apply the patch to the package. Is it possible to get this into Natty? It's a quite annoying bug which can be triggered quite easily. Once broken it's probably not that easy for inexperienced users to fix their systems.

Revision history for this message

Chris Coulson (chrisccoulson) wrote on 2011-03-07:

Thanks, will sponsor this!

Changed in metacity (Ubuntu):
assignee:	nobody → Chris Coulson (chrisccoulson)

Chris Coulson (chrisccoulson) on 2011-03-07

Changed in metacity (Ubuntu):
status:	Triaged → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-03-07:

This bug was fixed in the package metacity - 1:2.30.3-0ubuntu6

---------------
metacity (1:2.30.3-0ubuntu6) natty; urgency=low

* debian/patches/19_initialise_all_workspace_names.patch
Added patch from upstream. (Closes LP: #583847)
-- Jan Brinkmann <email address hidden> Sun, 06 Mar 2011 12:54:45 +0000