Fcitx Error after Login (KDE/Wayland)

General system Newbie
1

Hello all,

I’ve been running EndeavourOS with KDE Plasma since early December and so far it’s been a great experience. However, today after a system restart I started seeing this error pop-up after login:

Fcitx should be launched by KWin under KDE Wayland in order to use Wayland input method frontend. This can improve the experience when using Fcitx on Wayland. To configure this, you need to go to “System Settings” → “Virtual keyboard” and select “Fcitx 5” from it. You may also need to disable tools that launches input method, such as imsettings on Fedora, or im-config on Debian/Ubuntu. For more details see https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland#KDE_Plasma

I’m not familiar with Fcitx and I haven’t used any virtual keyboards. I navigated to “System Settings” → “Virtual keyboard” and found that my current selection is “None”. I see entries for “Fcitx Wayland Launcher (Experimental)” and “Fcitx 5”, which are not selected. I also see entries for “IBus Wayland” and “Maliit”, which are likewise not selected.

I searched the Arch Wiki for Fcitx5 and found that it’s apparently an input framework that seems to be used for typing characters that aren’t natively available on the system’s input devices (e.g., typing Chinese characters with an English keyboard). I don’t really have a use case for this and I’m not sure why this package would be installed on my system.

I just have a few questions around this:

  1. Is Fcitx a default package installed with EndeavourOS?
  2. What is it used for? Am I correct that it’s for typing foreign characters?
  3. What would be causing the above error to display after I log in?

Thanks in advance!

1 Like
2

Hello and welcome,

  1. No
  2. Yes
  3. I’m not using KDE nor Wayland, I have no idea.
3

Welcome to the forum :enos: :enos_flag:

Maybe you will find some answers in this thread.

4

You can take a look here: https://wiki.archlinux.org/title/Fcitx

**Warning:** Fcitx is now in maintenance mode.
5

I had no need for a virtual keyboard so I just made sure it was disabled.I am guessing it was pulled in with some other update.

6

For some reason Fcitx5 was pulled in on Cinnamon as well, I totally removed Fcitx5 without issues. Not saying to try this on KDE.

7

I just removed it as well on KDE as checking it was installed as an orphan.

1 Like
8

Thanks everyone for your answers, this was really helpful. I’ve marked straycat’s response as the solution as this worked for me. The thread linked by keescase above also provided some useful insight into this issue, specifically this post: Second keybord layout missing - #5 by Mandarine

3 Likes
9

I also kicked out everything related to fcitx on my KDE Plasma machine.

10

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.