After installing 4.2rc2 clean (I deleted all xfce configs before upgrading), one of the first things that bugged me was the key-binder of the shortcut editor. It sometimes does really weird things with meta keys. Let me explain some examples of this cases: 1. Press alt-f2 very fast (that is, press alt then f2 while holding alt then leave both). Shortcut becomes F2 sometimes. That happens when the user happens to leave alt before leaving f2, but since I tend to do it very fast, it happens often. 2. Try to define meta+space (l_evilkey + space). The user cannot, when space is pressed, the dialog is canceled (this combo is the default for run command on icewm... I'm somehow used to it). The user can define alt+space, shift+space, etc. without problems, tho. Also, space _alone_ can be defined, if he presses alt-space, then leaves first alt then space.
1. seems a gdk bug to me 2. apparently your meta key isn't seen as a modifier (see with xev or xmodmap)
Looks like it _IS_ a modifier: tux@nyu ~ $ xmodmap xmodmap: up to 4 keys per modifier, (keycodes in parentheses): shift Shift_L (0x32), Shift_R (0x3e) lock Caps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1 Alt_L (0x40), Alt_L (0x7d), Meta_L (0x9c) mod2 Num_Lock (0x4d) mod3 mod4 Super_L (0x73), Super_R (0x74), Super_L (0x7f), Hyper_L (0x80) mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x7c) Also, I use "Evil_L" + <1-4> for desktop switching; they work fine in 4.2rc2. If it helps at all, meta+space was what I used with xfce4 4.0.x. If it's of any use: KeyPress event, serial 31, synthetic NO, window 0x2400001, root 0x8f, subw 0x400061, time 14606027, (127,44), root:(1546,951), state 0x10, keycode 115 (keysym 0xffeb, Super_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 31, synthetic NO, window 0x2400001, root 0x8f, subw 0x400061, time 14606185, (127,44), root:(1546,951), state 0x50, keycode 65 (keysym 0x20, space), same_screen YES, XLookupString gives 1 bytes: (20) " " XmbLookupString gives 1 bytes: (20) " " XFilterEvent returns: False KeyRelease event, serial 31, synthetic NO, window 0x2400001, root 0x8f, subw 0x400061, time 14606280, (127,44), root:(1546,951), state 0x50, keycode 65 (keysym 0x20, space), same_screen YES, XLookupString gives 1 bytes: (20) " " KeyRelease event, serial 31, synthetic NO, window 0x2400001, root 0x8f, subw 0x400061, time 14606325, (127,44), root:(1546,951), state 0x50, keycode 115 (keysym 0xffeb, Super_L), same_screen YES, XLookupString gives 0 bytes: is what I get from pressing and releasing Evil_L + space.
Yeah, it's a modifier to X, but not to gtk/gdk, I think. We'll have to look into it a bit closer to see what's going on.
See that thread for more details : http://foo-projects.org/pipermail/xfce4-dev/2006-April/019880.html You should close that bug as "wontfix", it's adk/gdk issue that should be fixed in gtk+ 2.10
it's a bug in gdk/atk (should be fixed in gtk 2.10) (cfr. comments from Olivier in code and ML)
As of today, I'm using GTK+ 2.10.6 and it isn't fixed yet.
It works in gdk/gtk+-2.10.x, tested.
I mean, the Windows key as modifier works in xfce 4.4/gtk+-2.10.x - Unfortunately, I don't have time/resource/willing to test of fix that in 4.2.