Hi,
This was reported by a Debian user. Please retain the CC to
540577-forwar...@bugs.debian.org in your response, in order that
the Debian BTS has a record.
These days, the X server takes input from HAL regarding input
devices, and these events may happen at any time. Unfortunately, fvwm
never remaps keys, so keymaps appear to be wrong. This has been
discussed on the fvwm mailing lists before, I would just like to put on
record a wish list item.
Original problem symptoms:
-------- ------- ---------
It only appears at the first start reproduceable by calling
"/etc/init.d/kdm restart".
just for a test case this is the fvwm configfile ~/.fvwm/config:
"Key y A M Exec exec xeyes"
xorg.conf section:
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
Option "XkbVariant" "nodeadkeys"
EndSection
The de (german) qwertz keyboard works and all applications get the
right keycode. "z" on the keyboard gives a "z" when you hit
it, "y"-key a "y", and so on.
But now it gets strange: If I hit "Alt+y" nothing happens. But
if I hit "Alt+z" xeyes shows up. But if numlock is activated, even
"Alt+z" doesn't work.
Just for testing:
- /etc/init.d/dbus stop (stops hald too)
-> same problem
- In xserver-xorg-input-kbd changed default keymap to "de"
-> same problem
Additional information:
---------- ------------
Anyway, it turns out that all programs loaded before the
keyboard map is initialized will not see the new keyboard map.
The fix is simple. Just run setxkbmap / xmodmap / whatever you use
*before* any X clients (including fvwm) are loaded. For example, in my
~/.xinitrc:
which setxkbmap >& /dev/null && setxkbmap us
[[ -f ~/.xmodmaprc ]] && xmodmap ~/.xmodmaprc
...
exec fvwm
manoj
--
For those who like this sort of thing, this is the sort of thing they
like. Abraham Lincoln
Manoj Srivastava <sriva...@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
