Version: (using KDE KDE 3.5.3) Installed from: Gentoo Packages Compiler: gcc 3.4.6 OS: Linux When Xorg 7.1 evdev driver is used for keyboard, some keys doesn't work correctly in KDE. In twm with same X configuration these keys work fine. The keys that aren't working are the arrows, Alt Gr, Insert, Delete, PgUp, PgDn, Home, End, Numeric Enter. When NumLock is switched off PgUp, PgDn, Home etc. on numeric keypad can be used, but it's not very confortable. In kxkb shortcut assign application can be discovered, that some keys are not mapped properly - for example Alt Gr send numpad Enter signal, left arrow behaves like Win key. But some keys doesn't do anything. When standard keyboard driver in X is used, everything works ok.
Do they work in a plain Qt application?
If you mean by the plain Qt application to run for example konqueror without KDE (from pure X (using failsafe session from kdm)), then I must report, that everything works fine. Now I'll add full list of problematic keys with bad mappings discovered using kde key shortcuts editor: KEY BAD MAPPING ------------------------- Alt Gr KP_Enter Right Ctrl Page Down Print Screen Delete Pause - (doesn't react) Insert - Home Pause Page Up KP_Divide Delete - End Win + Page Down Menu Left Alt + Up Print Screen Down Win + Right - Left Win key - Right Win key - Menu key - KP_Divide Insert KP_Enter Down Other keys are OK
I must also apologize for bad information in my report - I've written that left arrow key sends win key, that's a mistake. Left arrow key sends Alt key and down arrow key sends Win key - the table in comment #2 is 100% right. Sorry
No, I meant an application that doesn't link to the KDE libraries, like Skype, Google Earth, Qt Designer or even "qtconfig".
So I've tried GIMP, Ethereal (both GTK) and XILINX ISE WebPack (don't know what library is used, but it's not qt nor gtk) - same results - bad key mapping with evdev driver, right key mapping with the classical one.
Not a KDE problem then. Your problem must be in some lower layer, like X11 itself.
Thiago Macieira is right. This problem can _mostly_ be fixed by setting the XkbModel to evdev (for example by adding the line option "XkbModel" "evdev" into the keyboard section of your /etc/X11/xorg.conf) However, one bug remains and it's _extremely_ annoying: http://bugs.kde.org/show_bug.cgi?id=125559
The problem seems to be that something in the KDE keyboard configuration screws up the keycode mapping in the X server: if I load KDE from an xterm and then close it down again, the keyboard is screwed up until I run "setxkbmap -keycodes evdev".
Created attachment 18558 [details] a workaround to auto-run setxkbmap Here's a work-around until the actual bug is fixed: this .desktop runs "setxkbmap -keycodes evdev -model evdev"; drop it in your ~/.kde/Autostart and it will (largely) fix your keyboard after you restart KDE. You'll also need to rebuild with my patch from bug 125559 to keep the up-key from triggering KSnapshot.
I had excactly this problem. It took me some time to figure out, that I had to go to the locale settings in the Kontrolcenter and choose keyboard model "Evdev-managed keyboard" in order to make the keys you mention work. Still, the "up arrow" is confused with "PrintScrn". But this is another story, explained and apparently fixed in bug 125559.