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 670847 - Keyboard shortcuts can only be set for existing workspaces
Keyboard shortcuts can only be set for existing workspaces
Status: RESOLVED DUPLICATE of bug 663431
Product: gnome-control-center
Classification: Core
Component: Keyboard
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-26 20:28 UTC by blubbla
Modified: 2012-02-26 21:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description blubbla 2012-02-26 20:28:36 UTC 
When trying to set the shortcuts for switching to another workspace or moving windows to another workspace, you can only set the shortcuts for existing workspaces.

This made sense in gnome 2 which had a fixed number of workspaces, but is annoying in gnome 3 when you're configuring the shortcuts, as you need to move windows to new workspaces first.
Comment 1 Bastien Nocera 2012-02-26 21:06:43 UTC 
Was already fixed for GNOME 3.4.

commit be4e40bf99c0c89a40fa54ab9c73176d3f432a1a
Author: Florian Müllner <fmuellner@gnome.org>
Date:   Fri Nov 4 21:06:49 2011 +0100

    keyboard: Remove support for conditional shortcuts
    
    Keyboard shortcut definitions could specify a condition to determine
    whether it should be shown in the UI or not. This was only used by
    Metacity/Mutter, to make the visibility of some shortcuts depend on
    the number of workspaces. However, as workspaces are now managed
    dynamically in GNOME 3, the frequent changes to the list of shortcuts
    have become rather confusing, so a fixed list of shortcuts is used now.
    
    With the only consumer of conditional shortcuts gone, there's no reason
    to keep the feature around.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=663431

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