Out of bound keycode

[wismill]

Originally posted by @sundermann in #626 (comment):

Is it correct that an out of bounds key fails xkb_keymap_new_from_string? The log message indicates that the key was just ignored but this completely errors out creating a keymap. Is this intended? I am hitting this when parsing a keymap provided by the wayland compositor on webOS in Kodi:

2025-08-19 14:41:09.075 T:6803    error <general>: [xkb] Keycode too big: must be < 0xfff, got 0x5030; Key ignored
2025-08-19 14:41:09.075 T:6803    error <general>: [xkb] Failed to compile xkb_keycodes                                                   
2025-08-19 14:41:09.075 T:6803    error <general>: [xkb] [XKB-822] Failed to compile keymap

[wismill]

@sundermann Could you provide your keymap? Where do you get your keycodes from? E.g. on Linux keycodes are currently limited to 0x2ff.

[sundermann]

Keymap: https://paste.kodi.tv/qolemipuca Keycodes are provided by the wayland compositor.

<IR_VIRKEY_TEXTHOLD> = 20528; This is the only key that is out of bounds and we do not really care about it. It's ok to be ignored but the constructing of the keymap ideally shouldn't fail due to the key being ignored. This was working fine but we bumped our libxkbcommon in kodi recently revealing this behaviour change.

[sundermann]

Added a small patch to our depends buildsystem but it would be great if the issue could be resolved upstream. xbmc/xbmc#27128