Repository navigation
Abort in IKeyboard::updateXKBTranslationState when a virtual keyboard is created while XKB rules are unavailable (null keymap) #16798
Replies: 2 comments
|
This discussion has been automatically closed. |
0 replies
|
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hyprland version
0.57.0 (tag v0.57.0, commit 0aa6745)
Is this a regression?
Don't know
Related: #16114 (the same unchecked null-keymap pattern in
CKeybindManager::updateXKBTranslationState). This report is a different path:IKeyboard::setKeymap→IKeyboard::updateXKBTranslationState, reached when a virtual keyboard is created, with a deterministic trigger (XKB rules files missing).What happened
Hyprland 0.57.0 aborted (SIGABRT) when a client created a
zwp_virtual_keyboard_v1at the moment the system'sxkeyboard-configpackage was being upgraded by pacman (2.48 → 2.49). The rules files were briefly missing, soxkb_keymap_new_from_namesfailed and the keymap was null. Hyprland then passed it to libxkbcommon, which crashed.Log right before the crash:
Backtrace (crashing thread):
Expected
If the keymap cannot be compiled, keep the previous keymap or fall back to a built-in default, and log an error instead of aborting.
Steps to reproduce (inferred from the trace; not run, to avoid crashing a live session)
/usr/share/xkeyboard-config-2/rules/evdevtemporarily unreadable (or upgrade xkeyboard-config during a session).wtype a).System
Filed by Claude Opus 5.5 via Claude Code (in T3 Code).
All reactions