https://bugzilla.redhat.com/show_bug.cgi?id=2157582
--- Comment #6 from Andrew Gunnerson <accounts+fedora(a)chiller3.com> ---
Thanks. so if you put QT_IM_MODULE=fcitx into some file under
$HOME/.config/plasma-workspace/env, logout and login, you can use fcitx on Plasma Wayland,
right?
Yep, I tested a few ways and these all work for me (after a single log out +
log in):
1. Setting environment variables directly in
~/.config/plasma-workspace/env/imsettings.sh
export XMODIFIERS=@im=fcitx5
export GTK_IM_MODULE=fcitx5
export QT_IM_MODULE=fcitx5
2. Loading imsettings' own scripts in
~/.config/plasma-workspace/env/imsettings.sh. I also had to edit
/usr/libexec/imsettings-functions so that is_{gtk,qt}_supported don't check for
the systemd module in wayland.
source /usr/libexec/imsettings-functions
log_init
setup_gtk_immodule
setup_qt_immodule
setup_xim
3. Setting systemd environment variables with systemd in
~/.config/environment.d/fcitx.conf
XMODIFIERS=@im=fcitx5
GTK_IM_MODULE=fcitx5
QT_IM_MODULE=fcitx5
(I personally prefer 3 since it's (seemingly) more desktop-agnostic. If you'd
be willing to go back to that approach, are there more details about the issues
encountered with it? I'd be happy to help fix them.)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2157582