On Mon Jun 15 06:42:48 2026 +0000, Etaash Mathamsetty wrote:
Yeah, it doesn't make any sense for this to happen. But the protocol doesn't define any behavior related to this case: https://wayland.app/protocols/wayland#wl_keyboard:event:modifiers and https://wayland.app/protocols/wayland#wl_keyboard:event:keymap. Which IMO makes it a case that we should avoid a crash (and just not update the state?). Not sure what the client is supposed to do here, perhaps do nothing would be a valid behavior? IMO it would be better to fix it in the compositor (and update the protocol spec if necessary). Other calls such as set_current_xkb_group might have side effects that expect keyboard layouts, and therefore keymap, to have been initialized. Otherwise we just hide the bug in Wine and it might never be properly fixed.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/11151#note_143099