Bug 442811

Summary:	Shortcut key for changing keyboard layout does not work when there are 3 layouts.
Product:	[Applications] systemsettings	Reporter:	Andy Great <andythe_great>
Component:	kcm_keyboard	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	butirsky, nate
Priority:	NOR
Version:	5.22.4
Target Milestone:	---
Platform:	Other
OS:	Other
See Also:	https://bugs.kde.org/show_bug.cgi?id=432436
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Andy Great 2021-09-22 17:35:29 UTC

SUMMARY
When there are 3 keyboard layout (eg. English (US), Thai, Swedish), using change layout shortcut does cycle from Swedish to English (US)

STEPS TO REPRODUCE
1. Go to system settings > Input devices > Keyboard
2. Go to layouts tab
3. Add English (US), Thai, Swedish layouts.
4. Set main shortcut to Win+Space > Apply
5. Press Win+Space to change layout starting from English (US).
6. Layout will switch to English (US) > Thai > Swedish but does not go back to English (US).
7. Remove Swedish layout will cycle between English and Thai normally. 

OBSERVED RESULT
Using shortcut will stuck at Swedish layout.

EXPECTED RESULT
Layout should cycle back from Swedish to English (US).

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210915
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.2-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 4600H with Radeon Graphics
Memory: 7.1 GiB of RAM
Graphics Processor: AMD RENOIR

Comment 1 Andrey 2021-09-22 20:57:13 UTC

I tried your setup on Wayland and got somewhat different result:
switching stuck on Thai using Win+Space main shortcut,
but works OK with Capslock as I have it as my main shortcut also.

Anyway, this is probably upstream issue with XKB configuration files of particular layout.
Similar was already reported: see bug 432436.
I suggest to report upstream, as it was done here:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/252

Comment 2 Nate Graham 2021-09-27 13:53:52 UTC


*** This bug has been marked as a duplicate of bug 432436 ***