Bug 509637 - Improve XKB keymap error management
Summary: Improve XKB keymap error management
Status: CONFIRMED
Alias: None
Product: kwin
Classification: Plasma
Component: input (other bugs)
Version First Reported In: 6.4.4
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2025-09-18 13:35 UTC by fabrice salvaire
Modified: 2025-09-18 20:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fabrice salvaire 2025-09-18 13:35:18 UTC
Actually, the Wayland experience for a custom keymap is worse than for the Xserver.

If the corresponding symbol file in /usr/share/X11/xkb/symbols cannot be read (permission) then Plasma crashes so badly that we have to reboot the computer using a kernel Ctrl+Alt+Del.

After a major upgrade, it is common that a xkb update breaks the custom keymap.  In this case, Kwin only reports errors in /var/log/message, doesn't show any UI error message and uses the next keymap as a fallback.

KDE settings experience is also bad :
- It resets the keymap list when we disable it
- We have to change the keymap list order to make fix and try until it works as expected
- It reports any errors

On Linux, I would expect a command line and UI that reports a comprehensive error and a fallback to an internal US keymap or a clean session abort.