From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Kq63W-0004BC-1B for garchives@archives.gentoo.org; Wed, 15 Oct 2008 13:04:52 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 109E8E02E5; Wed, 15 Oct 2008 13:04:45 +0000 (UTC) Received: from mail.askja.de (mail.askja.de [83.137.103.136]) by pigeon.gentoo.org (Postfix) with ESMTP id BA704E02E5 for ; Wed, 15 Oct 2008 13:04:44 +0000 (UTC) Received: from static-87-79-89-40.netcologne.de ([87.79.89.40] helo=zone.wonkology.org) by mail.askja.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1Kq63O-0002Ji-CO for gentoo-user@lists.gentoo.org; Wed, 15 Oct 2008 15:04:42 +0200 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by zone.wonkology.org with local; Wed, 15 Oct 2008 15:04:38 +0200 id 0001033E.48F5EA66.00003F3C From: Alex Schuster Organization: Wonkology To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] KDM: Keyboard problems after X update Date: Wed, 15 Oct 2008 15:04:32 +0200 User-Agent: KMail/1.9.9 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200810151504.34699.wonko@wonkology.org> X-Archives-Salt: 2d18f9e6-d997-4a3f-a6e9-23131daeee71 X-Archives-Hash: 9389aba3aca4816ea9ff0d33b4d65f75 Hi there! I'm in the middle of a world update, but X stuff seems to be updated now.=20 The problem is that the keyboard does not work as before. It's a german keyboard. Here are expected keys, and the results: =DF \ =F6 [ =E4 ] =FC @ Keys like @ (Alt-Gr q), | (Alt-Gr <) and ~ (Alt-Gr +} do not work at all.=20 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:=20 Other) (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap [...] There are quite some references to this message, but many are unresolved.=20 Someone installed xkbutils, this did not help me, and I do not see why it=20 should. Some people xmodmap a lot, but this would be a workaround, while=20 I am interested in a cleaner solution. The weird thing is that this happens only when using KDM, not if I startx=20 from the text console. Does this ring a bell for someone? Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XKbModel" "pc105" Option "XKbLayout" "de" Option "XKbVariant" "nodeadkeys" EndSection Wonko