Bug Reports: changing X keymaps disrupts xmonad keybindings
G'day. Just a quick bug report: Changing X keymaps between, say, dvorak and us, using setxkbmap will often (though not always) break xmonad keybindings. I haven't been able to discern any pattern with when it will break the bindings and when it won't. Getting keybingings to work again is as simple as using setxkbmap over and over until the keybindings work again. ie setkbmap will break the bindings, but it will also fix them when they're broken. Another bug report (though one which has probably been noticed by someone else): killing xmonad and restarting it seems to lose management of all windows that are not being managed by workspaces currently visible on any screens.
Another bug report (though one which has probably been noticed by someone else): killing xmonad and restarting it seems to lose management of all windows that are not being managed by workspaces currently visible on any screens.
That should definitely not occur, though it is a symptom of an issue in the darcs branch about a month ago. You're running latest, clean X11-extras and xmonad? -- Don
On Thursday 12 July 2007 08:09:43 Robert Marlow wrote:
G'day. Just a quick bug report:
Changing X keymaps between, say, dvorak and us, using setxkbmap will often (though not always) break xmonad keybindings. I haven't been able to discern any pattern with when it will break the bindings and when it won't.
Getting keybingings to work again is as simple as using setxkbmap over and over until the keybindings work again. ie setkbmap will break the bindings, but it will also fix them when they're broken.
Yeah, there's something funny with our handling of MappingNotifyEvent and refreshKeyboardMapping. I haven't had time to look at this yet (and would appreciate help in this area!).
Another bug report (though one which has probably been noticed by someone else): killing xmonad and restarting it seems to lose management of all windows that are not being managed by workspaces currently visible on any screens.
This should be fixed in the latest xmonad, make sure you've got this patch:
Fri Jun 29 21:10:26 CDT 2007 Spencer Janssen
On Thursday 12 July 2007 08:09:43 Robert Marlow wrote: Yeah, there's something funny with our handling of MappingNotifyEvent and refreshKeyboardMapping. I haven't had time to look at this yet (and would appreciate help in this area!).
I'd offer to help but I can't foresee myself having the time anytime soon. I'll have a look if I get a chance though.
This should be fixed in the latest xmonad, make sure you've got this patch:
I'm sorry; I should know better. It slipped my mind that my setup had gotten out of date on the computer I was experiencing the problem with. I've upgraded it and will keep an eye out to see if it comes up again.
participants (3)
-
dons＠cse.unsw.edu.au -
Robert Marlow -
Spencer Janssen