Bug 444051

Summary: Extra "empty" layouts in Wayland session when option "Right Alt never chooses 3rd level" is selected
Product: [Plasma] kwin Reporter: Yaroslav Sidlovsky <zawertun>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: butirsky, zawertun
Priority: NOR    
Version: 5.23.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
URL: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/merge_requests/253
See Also: https://bugs.kde.org/show_bug.cgi?id=440027
https://github.com/xkbcommon/libxkbcommon/issues/262
Latest Commit: Version Fixed In:
Attachments: Screenshot of the issue

Description Yaroslav Sidlovsky 2021-10-19 14:51:36 UTC
Created attachment 142629 [details]
Screenshot of the issue

SUMMARY
Initially I have 2 layouts in my system: "us" and "ru".
When using option "Right Alt never chooses 3rd level" in Wayland session appears 2 more "empty" layouts, see attached screenshot.

When switching to the empty layouts I observe such behaviour:
1. first empty layout corresponds to "us" (English);
2. second empty layout corresponds to "ru" (Russian).

Under X11 session same option don't cause such issues.

STEPS TO REPRODUCE
0. Login to the Wayland KDE session;
1. Exec "kcmshell5 kcm_keyboard" (Keyboard KCM);
2. Go to tab "Advanced", enable option "Right Alt never chooses 3rd level" under "Key to choose the 3rd level" tree;
3. Click button "Apply".

OBSERVED RESULT
4 layouts appears - 2 correct and 2 "empty".

EXPECTED RESULT
No extra "empty" layouts should be shown.

SOFTWARE/OS VERSIONS
Operating System: Fedora 34
KDE Plasma Version: 5.23.0
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.11-200.fc34.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 31.2 ГиБ of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Comment 1 Andrey 2021-10-19 15:00:11 UTC
Possible fix design on the library side was reported upstream:
https://github.com/xkbcommon/libxkbcommon/issues/262#issuecomment-945665443
Comment 2 Andrey 2021-10-25 11:23:19 UTC
While it was considered as arguably a bug in libxkbcommon, this can be solved on XKB configuration side:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/merge_requests/253
Comment 3 Andrey 2021-11-12 16:59:42 UTC
Apparently has been fixed upstream:
https://github.com/freedesktop/xkeyboard-config/commit/29f2cd1eecc540480fcaf4580bcdd78283734e31