Difference between revisions of "Translations:Using Fcitx 5 on Wayland/48/en"
Jump to navigation
Jump to search
(Importing a new version from external source) |
(Importing a new version from external source) |
||
Line 1: | Line 1: | ||
=== KDE Plasma === | === KDE Plasma === | ||
Best setup: | Best setup: | ||
− | * KDE Plasma 5.27 | + | * KDE Plasma 5.27 or later |
* Environment variables: | * Environment variables: | ||
** Set <code>XMODIFIERS=@im=fcitx</code> for XWayland application | ** Set <code>XMODIFIERS=@im=fcitx</code> for XWayland application |
Latest revision as of 05:49, 11 June 2025
KDE Plasma
Best setup:
- KDE Plasma 5.27 or later
- Environment variables:
- Set
XMODIFIERS=@im=fcitx
for XWayland application - Start fcitx5 by go to "System settings" -> "Virtual keyboard" -> Select Fcitx 5
- Do not set
GTK_IM_MODULE
&QT_IM_MODULE
&SDL_IM_MODULE
. You could unsetGTK_IM_MODULE
&QT_IM_MODULE
by runingim-config
and then selectingdo not set any IM from im-config and use desktop default"
- Run chromium/electron application with
--enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime
- Set
- Caveats:
- Certain Gtk/Qt application that only works under X11 may still need to set
GTK_IM_MODULE
orQT_IM_MODULE
for them individually. - If you set
GTK_IM_MODULE/QT_IM_MODULE
globally, you will hit this issue Candidate window is blinking under wayland with Fcitx 5
- Certain Gtk/Qt application that only works under X11 may still need to set