Test case: 1) setxkbmap -layout us -model applealu_ansi 2) Use "numeric keyboard" in a terminal, it enters numbers as expected and "num lock" key has no effect - this apparently is the expeced behaviour on this keyboard model. 3) run libxkbcommon/test/interactive-x11, use "numeric keyboard", it prints: keysyms [ KP_Begin ] unicode [ ] layout [ USA (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ KP_Right ] unicode [ ] layout [ USA (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ KP_Left ] unicode [ ] layout [ USA (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ KP_Right ] unicode [ ] layout [ USA (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ KP_Begin ] unicode [ ] layout [ USA (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ KP_Left ] unicode [ ] layout [ USA (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ KP_Next ] unicode [ ] layout [ USA (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ KP_Begin ] unicode [ ] layout [ USA (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ KP_Left ] unicode [ ] layout [ USA (0) ] level [ 0 ] mods [ ] leds [ ] But should print: KP_<number> For referance: https://bugreports.qt-project.org/browse/QTBUG-41823
Thanks, this is fixed in https://github.com/xkbcommon/libxkbcommon/commit/30e7445d846e45f68dd21fd6d954eb7806adc8bd. Will be in v0.5.0 (should be released soon). I also sent some patches for xkeyboard-config related to this issue: https://bugs.freedesktop.org/show_bug.cgi?id=85114 but these are not needed for things to work properly.
Tested and it works now as expected. Thanks.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.