Can't Disable Custom Keyboard Setting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I can't disable the default key binding for <Control><Alt>t ("Launch Terminal") from gnome-control-
Steps to reproduce:
0. mutter-common should be installed for these steps to exhibit the bug.
1. Type "gnome-
2. Click on "Keyboard" -> "Shortcuts" -> "Custom Shortcuts".
There should be a binding for "Launch Terminal". I wanted to disable this binding.
3. Click on the "Launch Terminal" line, and dismiss the dialog it pops up.
4. Now click on the "-" button. The binding will disappear from the list.
5. Close the control center and hit Ctrl-Alt-t in the app of your choice (I used emacs).
Expected behavior: terminal should no longer start; the currently focused application should get the keys. gnome-control-
Actual behavior: terminal starts; the application doesn't see the keys. If you start gnome-control-
It is possible to change the keys bound to "Launch Terminal", and it is possible to change the action taken when this shortcut is fired. Those changes stick. But removal of the binding is always silently undone.
Possible cause: I don't know enough about gconf to say for sure, but it seems like settings introduced in /usr/share/
Workaround: Uninstall mutter-common. Or, set "Launch Terminal" to a key that you'll never press, like Ctrl+Alt+Shift+F12.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Fri Jun 8 17:58:54 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012)
SourcePackage: gnome-control-
UpgradeStatus: Upgraded to precise on 2012-05-17 (22 days ago)
usr_lib_
activity-
deja-dup 22.0-0ubuntu2
gnome-bluetooth 3.2.2-0ubuntu5
indicator-datetime 0.3.94-0ubuntu2
Related branches
affects: | gnome-control-center (Ubuntu) → gnome-shell (Ubuntu) |
Status changed to 'Confirmed' because the bug affects multiple users.