Bug ID | 1084804 |
---|---|
Summary | Plasma + Wayland: input method does not start |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 15.0 |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Major |
Priority | P5 - None |
Component | KDE Workspace (Plasma) |
Assignee | opensuse-kde-bugs@opensuse.org |
Reporter | ftake@geeko.jp |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
On Plasma + Wayland session, input method like IBus, Fcitx does not start anymore. This is simply because /etc/X11/xim, which has been a script to launch one of input methods, is not executed on a Wayland session. So we need to update our input method launcher script to support Wayland. How can we do that? What is the right way to set environment variables such as GTK_IM_MODULE and QT_IM_MODULE according to the current selected input method under on Wayland session? Workaround: Set GTK_IM_MODULE and QT_IM_MODULE in ~/.i18n and start ibus-daemon -xd or fcitx by using KDE auto start settings. However, both IBus and Fcitx will not work correctly due to other bugs and limitations related to Wayland.