Help: KDE keymap crazyness

[riaan]

Hi Uwe

I'm experiencing somethinf frustrating and weird on my box at home. Most of the keys to the right of the main Enter key, i.e. arrows, Print Screen, Home, End, Num Lock, Keypad Enter, etc. are mapping to the wrong keycodes! This probably happened during one of the recent updates.

I investigated with "xmodmap -pke" and "xev" and the xevents produced by the keyboard on these keys do not correspond to those output by the xmodmap file! E.g., the "Up" arrow key (supposed to be keycode 98) produces Xevent 111, i.e. "Print Screen" and "Print Screen" (keycode 111)  produces xevent 107, i.e. "Delete", and many more!

It seems that KDE is responsible because if I log in in "failsafe", i.e. X without a WM, then everything is OK. But as soon as I log into KDE then the keymap's crazy again.

My X keyboard layout is set to "Generic 105-key" and I'm using KDE's Keyboard Layout to switch between US basic (usb) and US intl (usi) layout variants as needed. I've been doing this for many-many years now.

Any idea why? And how to fix it?

Any Info will help. ProfGoogle is no help as I can't get such an error anywhere. Maybe my search strings are wrong.

Regards
Riaan

[riaan]

Hi Uwe, all

My apologies. This does not seem to be a fault of KDE 3.5. The weird keymapping persists even without KDE. It is just that the weird arrow keycodes produce the expected reaction in the command line (recalling commands and left and right to edit) without KDE, but with KDE running they do not.

Regards
Riaan

[uwe]

Had the same problem recently. An
emerge --update --deep world
solved it for me.

Uwe

[riaan]

Hi Uwe

My Laptop and OfficePC are both fine - it is just my HomePC that has the problem. I always do deep updates (emerge -DuNav world), but this was not enough. Look at these links:
http://forums.gentoo.org/viewtopic-p-4749002.html?sid=de3ef40ae793c76cb40ed3083e63963f
http://de.pastebin.ca/848315
http://forums.gentoo.org/viewtopic-t-641870.html
It seems that the 'culprit' is HAL and hal-info, the new (unstable) versions, that is. I probably have to just check my use flags, specifically the "hal" use flag and then deep update with newuse. There are also other things to try in the above links if that does not work.

Regards and thanks
Riaan

[riaan]

Uwe

Just to let you know, masking the newest hal, hal-info and xf86-input-evdev solved it for me:
   >=sys-apps/hal-0.5.10
   >=x11-drivers/xf86-input-evdev-1.2.0
   >=app-misc/hal-info-20071011
"genlop -l" showed that I emerged these on Wednesday and that is when and where where my problems started. I don't like this, but I know, I know: "It's the unstable tree and one shouldn't complain..." - still ...

Regards
Riaan