KDM: Keyboard problems after X update
Did emerge told you to update some config files?
On Wed, Oct 15, 2008 at 3:04 PM, Alex Schuster <firstname.lastname@example.org> wrote:
I'm in the middle of a world update, but X stuff seems to be updated now.
The problem is that the keyboard does not work as before.
It's a german keyboard. Here are expected keys, and the results:
Keys like @ (Alt-Gr q), | (Alt-Gr <) and ~ (Alt-Gr +} do not work at all.
Same goes for console switching via Ctrl-Alt-Fn.
There is a warning message in the X log, I assume this has to do with it:
(**) Option "CoreKeyboard"
(**) Keyboard0: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "de"
(**) Keyboard0: XkbLayout: "de"
(**) Option "XkbVariant" "nodeadkeys"
(**) Keyboard0: XkbVariant: "nodeadkeys"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type:
(WW) Couldn't load XKB keymap, falling back to pre-XKB keymap
There are quite some references to this message, but many are unresolved.
Someone installed xkbutils, this did not help me, and I do not see why it
should. Some people xmodmap a lot, but this would be a workaround, while
I am interested in a cleaner solution.
The weird thing is that this happens only when using KDM, not if I startx
from the text console. Does this ring a bell for someone?
* * * *Identifier *"Keyboard0"
* * * *Driver * * *"kbd"
* * * *Option * * *"XKbModel" * "pc105"
* * * *Option * * *"XKbLayout" *"de"
* * * *Option * * *"XKbVariant" "nodeadkeys"
* * * *Wonko