Date: Wed, 11 Mar 2020 10:29:08 +0100 From: Niclas Zeising <zeising@freebsd.org> To: Greg 'groggy' Lehey <grog@FreeBSD.org>, Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: FreeBSD current users <FreeBSD-current@FreeBSD.ORG>, FreeBSD Stable Users <freebsd-stable@freebsd.org> Subject: Re: New Xorg - different key-codes Message-ID: <f130773f-7d68-2062-3ada-e9ebd888a5fe@freebsd.org> In-Reply-To: <20200311004635.GB89512@eureka.lemis.com> References: <6762.1583886003@critter.freebsd.dk> <20200311004635.GB89512@eureka.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-03-11 01:46, Greg 'groggy' Lehey wrote: > > On Wednesday, 11 March 2020 at 0:20:03 +0000, Poul-Henning Kamp wrote: > [originally sent to current@] >> I just updated my laptop from source, and somewhere along the way >> the key-codes Xorg sees changed. > > Indeed. This doesn't just affect -CURRENT: it happened to me on > -STABLE last week, so I'm copying that list too. See > http://www.lemis.com/grog/diary-mar2020.php?topics=c&subtitle=Daily%20teevee%20update&article=D-20200306-002910#D-20200306-002910 > , not the first entry on the subject. > >> I have the right Alt key mapped to "Multi_key", which is now >> keycode 108 instead of 113, which is now arrow left instead. > > Interesting. Mine wandered from 117 to 147, with PageDown ("Next") as > collateral damage. It seems that there are a lot of strange new key > bindings (partial output of xmodmap -pk): > > 117 0xff56 (Next) 0x0000 (NoSymbol) 0xff56 (Next) > 130 0xff31 (Hangul) 0x0000 (NoSymbol) 0xff31 (Hangul) > 131 0xff34 (Hangul_Hanja) 0x0000 (NoSymbol) 0xff34 (Hangul_Hanja) > 135 0xff67 (Menu) 0x0000 (NoSymbol) 0xff67 (Menu) > 147 0x1008ff65 (XF86MenuKB) 0x0000 (NoSymbol) 0x1008ff65 (XF86MenuKB) > > Some of these may reflect other remappings that I have done. > >> I hope this email saves somebody else from the frustrating >> morning I had... > > Sorry. I should have thought of reporting it. For me, with a number > of other issues, it was a frustrating week,some of which are still not > resolved. > This has to do with switching to using evdev to handle input devices on FreeBSD 12 and CURRENT. There's been several reports, and suggested solutions to this, as well as an UPDATING entry detailing the change. I'm sorry that it has caused fallout, but it is something that needs to be done in order to keep up with upstream graphics stack, and to improve FreeBSD desktop support in general. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196678 has some discussions regarding input devices, as does the x11@ mailing list archives. Regards -- Niclas Zeising FreeBSD Graphics Team
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f130773f-7d68-2062-3ada-e9ebd888a5fe>