https://bugzilla.redhat.com/show_bug.cgi?id=2076596
--- Comment #21 from Mike FABIAN mfabian@redhat.com --- (In reply to Harish Karumuthil from comment #20)
Hello all, I just want to share a quick & dirty fix for this problem. This is an external python script https://github.com/harish2704/dotFiles/blob/master/home/.local/Apps/daily- utils/bin/ibus-next-engine.py . It can switch to next input method if executed.
Add a custom global shortcut ( for eg: Super+Space ) entry in settings menu and put the above script as target command for the shortcut. We will get a minimal working Ibus in KDE plasma ( wayland )
Thank you!
But this does not switch the keyboard layout because ibus cannot switch the keyboard layout in KDE Wayland at the moment. I.e. you can switch between “real” ibus engines like ibus-m17n, ibus-anthy, ibus-typing-booster, ... with your script. For example, if that part in your script returns:
$ ibus read-config | grep preload-engines | sed "s/preload-engines://g; s/'/"/g" ["anthy", "m17n:t:latn-post", "kkc", "xkb:us:intl:eng", "xkb:mike::eng", "table:wubi-jidian86", "hangul", "libpinyin", "table:ipa-x-sampa", "typing-booster", "xkb:us:euro:eng", "xkb:de::deu", "table:cangjie5", "libzhuyin", "m17n:hi:itrans", "uniemoji", "m17n:t:unicode", "m17n:ru:translit", "m17n:mr:gamabhana", "xkb:ge::kat", "table:latex", "m17n:bn:national-jatiya", "OpenBangla", "table:jyutping"]
all the “engines” whose name starts with “xkb:” won’t work.