'Switch to Workspace NUM' key bindings no longer work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Compiz Core |
New
|
Undecided
|
Unassigned | ||
compiz (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I've been binding C-M-<NUM> to 'Switch to Workspace NUM' through the
(GNOME) keyboard bindings menu for several years now. As of a recent
Unity upgrade, this keyboard binding silently no longer works.
There are two issues here for me:
1) I can't find any way to undo, change or otherwise override Unity's
keyboard bindings.
2) A user who tries to set key bindings through the 'Systems Settings
-> Keyboard -> Shortcuts' is going to be very confused when the
shortcut he chose appears to have no, or the wrong effect, because
Unity is silently overriding the change.
I appreciate the answer to (1) may be some polite variation on "sucks
to be you" or "that's by design", but without wishing to be overly
dramatic, I have no idea how long it'll take me to undo over 5 years
of muscle memory.
And regardless of the outcome of (1), I think (2) is a real bug.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.2.0-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-15-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,
Date: Tue Feb 14 16:34:16 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: Upgraded to precise on 2012-01-09 (35 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 931927, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.