It definitive _not_ a bug in FVWM. FVWM is just faster than any other wm. I added a sleep(4) into main-function of FVWM and all works as expected.
So the bug is somewhere in the parallel start of window-manager + keymap setting. What packet is responsible for that? So the bug can be moved. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
