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 659764 - GNOME Shell shouldn't be changing metacity gconf num_workspaces
GNOME Shell shouldn't be changing metacity gconf num_workspaces
Status: RESOLVED DUPLICATE of bug 671568
Product: gnome-shell
Classification: Core
Component: general
3.1.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-21 20:22 UTC by Jeremy Bicha
Modified: 2012-03-07 16:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeremy Bicha 2011-09-21 20:22:11 UTC
As reported at http://pad.lv/826089 GNOME Shell uses the metacity gconf settings num_workspaces to keep track of how many workspaces are being used. Since GNOME Shell uses workspaces dynamically which is different from how nearly every other desktop manager works, GNOME Shell shouldn't be changing the global num_workspaces but should use a GNOME Shell specific variable.

Upon exiting GNOME Shell, the value is reset to 1. Because of this bug, workspaces are broken in all Metacity sessions (GNOME Fallback, Unity 2D, XFCE, etc.).
Comment 1 Florian Müllner 2012-03-07 16:15:00 UTC
Dup'ing on a newer bug which is more ambitious (i.e. to not write the num-workspaces setting anywhere, not just not using a schema shared with other wms)

*** This bug has been marked as a duplicate of bug 671568 ***