FS#62449 - [xkeyboard-config] Please revert XF86MonBrightnessCycle keysym commits to prevent internal errors
Attached to Project:
Arch Linux
Opened by Mort Yao (soimort) - Tuesday, 23 April 2019, 16:26 GMT
Last edited by Jan de Groot (JGC) - Sunday, 15 September 2019, 21:56 GMT
Opened by Mort Yao (soimort) - Tuesday, 23 April 2019, 16:26 GMT
Last edited by Jan de Groot (JGC) - Sunday, 15 September 2019, 21:56 GMT
|
Details
Description:
After upgrading to xkeyboard-config 2.26, X server randomly fails with the following log: /usr/lib/gdm-x-session[888]: Errors from xkbcomp are not fatal to the X server /usr/lib/gdm-x-session[888]: > Internal error: Could not resolve keysym XF86MonBrightnessCycle /usr/lib/gdm-x-session[888]: > This warning only shows for the first high keycode. /usr/lib/gdm-x-session[888]: > X11 cannot support keycodes above 255. /usr/lib/gdm-x-session[888]: > Warning: Unsupported high keycode 372 for name <I372> ignored Keyboard layout is reset when this happens as all existing xmodmap setting goes down. The cause of this failure is that the latest xkeyboard-config 2.26 release includes a commit ed67b29e [1] which assumes the existence of a matching keysym XF86MonBrightnessCycle in xorgproto. However, xorgproto (latest version 2018.4) has not been officially released with the required change [2] yet. I suggest patching xkeyboard-config to revert three related commits until a newer version of xorgproto gets released, as fixed in Debian [3]: - https://salsa.debian.org/xorg-team/data/xkb-data/raw/aaf547756a393f0a9ef74b4136ca4a2050e8c478/debian/patches/revert-Map-evdev-keycode-KEY_BRIGHTNESS_CYCLE.diff - https://salsa.debian.org/xorg-team/data/xkb-data/raw/b5f375a6e42d7aea2687914ec69d4cae8866731b/debian/patches/revert-Map-evdev-keycode-KEY_FAVORITES.diff - https://salsa.debian.org/xorg-team/data/xkb-data/raw/b5f375a6e42d7aea2687914ec69d4cae8866731b/debian/patches/revert-Map-evdev-keycode-KEY_KEYBOARD.diff Additional info: * package version(s): - xkeyboard-config 2.26-1, 2.26-2 - xorgproto 2018.4-1 * link to upstream bug report: - https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/161 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922020 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921940 [1] https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/commit/ed67b29e [2] https://gitlab.freedesktop.org/xorg/proto/xorgproto/commit/4e9f4e61 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921940 |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 15 September 2019, 21:56 GMT
Reason for closing: Fixed
Additional comments about closing: Bumped xkbcomp to git snapshot. Git contains fixes for warnings generated in this bugreport.
Sunday, 15 September 2019, 21:56 GMT
Reason for closing: Fixed
Additional comments about closing: Bumped xkbcomp to git snapshot. Git contains fixes for warnings generated in this bugreport.
Packages:
xkeyboard-config 2.27-1
xorgproto 2019.1-1
xorg-server-xvfb 1.20.5-2
$ xvfb-run -e /dev/stderr ls -la
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> ignored
> X11 cannot support keycodes above 255.
> This warning only shows for the first high keycode.
> Internal error: Could not resolve keysym XF86MonBrightnessCycle
> Internal error: Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server
(... results from ls -la ...)
To get rid of this message, at least xorg-xkbcomp should be recompiled.
This is the first time I report to ArchLinux, shall I comment your suggestion in https://www.archlinux.org/packages/extra/x86_64/xorg-xkbcomp/ or someone will be taking care of it from here?