The Wellspring
Solving the issue of Fcitx5 not working under Arch Linux KDE Wayland
ArchWaylandLinuxFcitx5

Solving the issue of Fcitx5 not working under Arch Linux KDE Wayland

By setting the KDE virtual keyboard to "Fcitx 5 Wayland Launcher", you can resolve the issue where the fcitx5 input method does not work in specific programs under the Wayland desktop environment.

189 views

On Arch Linux’s KDE Wayland environment, after a certain update, I found that many programs (especially those using the new Chromium kernel) cannot output Chinese using fcitx5. Even after modifying environment variables in /etc/environment or ~/.bashrc, Chinese input still cannot be activated.

After trying various solutions, including modifying multiple environment variables, I found a highly effective operation

Core Steps

  1. Open System Settings

  2. Navigate to Keyboard -> Virtual Keyboard

  3. Select Fcitx 5 Wayland Launcher (Experimental) from the list

  4. Click Apply and restart the session (I simply rebooted my computer)

image.png

Verification Results

After completing the settings and rebooting, open Alacritty and try to input Chinese. You will find that the Chinese input method can be perfectly activated.
image.png

Other Emergency Solutions

If the above “Virtual Keyboard” solution does not work for you, I have a working solution for Chromium kernels.
For applications using the Chromium kernel (such as Chrome, VS Code, etc.), you can add the --ozone-platform=x11 parameter at startup to force the program to run in XWayland compatibility mode.
image.png

It is worth mentioning that this method does not work for the Edge browser

Test Environment

  • OS: Arch Linux
  • Kernel: 6.18.2-zen2-1-zen
  • Desktop: KDE Plasma (Wayland)
  • Session: wayland
  • Fcitx Version: 5.1.17-1