Description of Problem: The bindings set up for sawfish by default do not work e.g. Activating the various workspaces, cycling windows, sending a window to the next workspace etc. How Reproducible: every time Steps to Reproduce: 1. start a gnome session 2. try to cycle open windows, or activate a new workspace 3. Actual Results: either nothing happens, or e.g. a tab is captured instead of alt-tab Expected Results: The bindings as listed in the sawfish configuration tool should work Additional Information:
hp... this works for me - however could this be that odd changing of meta keys we saw before?
What is your keymap like? Open "xev", type the Alt and Windows keys into it, paste in the output it has for KeyPress event. Is this a fresh install?
Here is the xev output: KeyPress event, serial 28, synthetic NO, window 0x2000001, root 0x32, subw 0x0, time 877267693, (788,362), root:(817,424), state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 characters: "" KeyRelease event, serial 28, synthetic NO, window 0x2000001, root 0x32, subw 0x0, time 877267802, (788,362), root:(817,424), state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 characters: "" KeyPress event, serial 28, synthetic NO, window 0x2000001, root 0x32, subw 0x0, time 877271248, (788,362), root:(817,424), state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES, XLookupString gives 0 characters: "" KeyRelease event, serial 28, synthetic NO, window 0x2000001, root 0x32, subw 0x0, time 877271333, (788,362), root:(817,424), state 0x40, keycode 115 (keysym 0xffeb, Super_L), same_screen YES, XLookupString gives 0 characters: "" This is from a new installation.
Thanks, I have no initial idea here. It has happened to a couple other people; I was hoping xev output would help :-( will try to investigate further.
I don't know how to reproduce this; moving to GNOME 2 soon so only critical fixes are going in to GNOME 1.x stuff. Possibly related to #54491 but I don't think it is the same bug.
*** Bug 54904 has been marked as a duplicate of this bug. ***