With ibus-1.5.29 in Fedora 29, QT_IM_MODULE and GTK_IM_MODULE should no longer be set for KDE Plasma Wayland. Can you make such a change to imsettings, please? Without that the behavior of ibus in Plasma Wayland is really bad. (This change should not be made for Plasma X11.) Reproducible: Always Steps to Reproduce: 1. env | grep MODULE Actual Results: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus Expected Results: GTK_IM_MODULE and QT_IM_MODULE to be unset in Plasma Wayland Related to https://fedoraproject.org/wiki/Changes/IBus_1.5.29
Do we still need it for X11, right?
(In reply to Akira TAGOH from comment #1) > Do we still need it for X11, right? Yes, we do.
One more question. This report requests to unset GTK_IM_MODULE too. does IBus 1.5.29 work without GSettings and GTK_IM_MODULE on Plasma-wayland?
(In reply to Akira TAGOH from comment #3) > One more question. This report requests to unset GTK_IM_MODULE too. does > IBus 1.5.29 work without GSettings and GTK_IM_MODULE on Plasma-wayland? Yes, it does. Those environment variables need to be unset.
Seems imsettings-plasma was dropped from @input-methods: https://pagure.io/fedora-comps/c/7553747fb0e4c1c6b97935dde1443e27de5fa3da?branch=main https://pagure.io/fedora-comps/c/98e56a9cf0425b76e9a0e8237113d87ad0b4cafa?branch=main So we may need to retest but this could this affect Plasma X11 aversely?
The way this gets set needs to be changed then to only activate when a Plasma X11 session is used. It currently does it unconditionally.
I'm going to update imsettings for this.
FEDORA-2023-adec06104c has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-adec06104c
FEDORA-2023-adec06104c has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-989df31081 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-989df31081
FEDORA-2023-989df31081 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
Just a note To get this fixed completely, we need to update ibus.conf too See #2233527
Working well so so far, thank you!!