From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218 Description of problem: The default keybindings (from a home directory created with 8.0, in case it matters) for `Move window to workspace [1234]' are <Control> <Alt> {exclam,at,numbersign,dollar}. These imply shift is depressed, and it causes the key sequences not to work. If I click on the shortcut and redefine it by pressing the appropriate sequences, I get <Shift> <Control> <Alt> {exclam,at,numbersign,dollar}, and from this point on, the shortcut works. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Try Ctrl-Alt-Shift-2, 2.Change the key binding to what the one you'd expect to work 3.Get <Shift> prepended to the sequence 4.Try it again Actual Results: 1. fails, 4. works. Expected Results: Either the default should be changed to something that works, or whatever interprets the sequence should be made smarter such that the current default (that looks saner) works. Additional info:
Hmm, strange. I'll look at it in metacity CVS and just let it trickle down to Red Hat eventually.
Looks like a bug in eggcellrendererkeys. It's now recording <shift>exclam instead of <shift>1. Changing the key in gconf-editor gives the proper result. I'll see if I can figure out what changed to cause this.
This was broken in 8.0 and no one noticed. There are two bugs here. 1) Metacity needs to check the keycode of it's events instead of the keysym. 2) The egg* code needs to try to store a more 'human understandable' key. Second part is filed upstream as: http://bugzilla.gnome.org/show_bug.cgi?id=103603 Moving this bug to metacity.
It appears that the defaults are gone from phoebe2, which at least hides the problem. However, setting the key sequences to say Ctrl-Alt-Shift-2 in keyboard shortcuts prefs gets us <Shift><Ctrl><Alt>at, and the shortcut doesn't work at all. One has to go to gconftool and change the at to 2 for it to work.
I see that, in Shrike, the shortcut works regardless of whether it says `2' or `at'. You still get `at' if you enter the shortcut in the keyboard, though, which is reasonable. If you really mean Shift 2 (in case at is not Shift 2), you can still set it with gconf-editor, so I guess we're ok.