GNOME Bugzilla – Bug 587290
Keyboard shortcuts doesn't work properly
Last modified: 2009-07-02 09:56:12 UTC
Please describe the problem: I tried to change shortcut for the "Move window to workspace 1" action. I changed it to the "Ctrl+Shift+!". After that I tried to reset this configuration (I pressed "Backspace" on this action, and it changed to the "Disabled"). But, this shortcut still works. It means, when I press "Ctrl+Shift+!" an active window moves to the first workspace. Even if I use this hotkey (in this example "Ctrl+Shift+!") for an other action, it still works as it was applied before (in this example for the "Move window to workspace 1"), and doesn't work for the new action at all. I guess the right behavior is to reset shortcut for an action, when it's in the "Disabled" state, and shortcut must not work anymore. Thanks in advance! /Regards, Alexander Steps to reproduce: 1. Set some shortcut for some action in the Keybindings preferences window 2. Try to use this hotkey (it should work) 3. Reset this hotkey (press "Backspace" on the action in the preferences window) 4. Try to use the hotkey again (it will work, but shouldn't) ---optional--- 5. Set the same (reseted before) hotkey to an other action 6. Try to use hotkey. It will run action you set in the first case. Actual results: I suppose after reseting any hot key it shell not work anymore. Expected results: Hotkeys work even after reseting. Does this happen every time? Yes, it's 100% reproducible for me. Other information: I don't use any type of the desktop effects. The window manager is default (Metacity).
Does the GConf key get updated when you disable the shortcut? In the "Move to ws 1" example you can check using gconftool-2 --get /apps/metacity/window_keybindings/move_to_workspace_1 Also, does this happen for all keybindings, or just window manager related stuff like this?
Hello Jens, here is my comment. First of all, this happen for all keybindings, I've just tried it for "Run terminal" action, and the problem was reproduced. the command: gconftool-2 --get /apps/metacity/window_keybindings/move_to_workspace_1 returns nothing... So, I have one more comment. Yesterday I tried it on my home netbook, and it was not reproduced! Well, on my netbook I have upgraded version of Ubuntu 9.04 (it was 8.10 before upgrade), and I have the same $HOME as I had in 8.10, but at work, I have Ubuntu 9.04 installed from scratch. It's the difference between my linux boxes. is it possible I don't have such kind of problem at my netbook because I have old $HOME, and I have old version of configuration files for Gnome?
"Run terminal" is, unfortunately, a bad example since it's handled by metacity as well. How about "Launch email client"? > the command: gconftool-2 --get > /apps/metacity/window_keybindings/move_to_workspace_1 > returns nothing... Ok, so that means g-c-c correctly resets the keybinding. I seem to remember earlier reports of metacity not always behaving correctly... > is it possible I don't have such kind of problem at my netbook because I have > old $HOME, and I have old version of configuration files for Gnome? Unlikely.
Hello Jens, You're completely right! I've just tried "Launch email client", and the problem was not reproduced! Well, I guess your suspicions are confirmed! And we have some problem with Metacity. Thanks for the investigation. Can I help your anyhow?
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 559816 ***