You are not logged in.
I have been attempting to get Japanese input working for hours with no luck.
I'm using KDE plasma 6.5.3 and Arch 6.17.8-arch1-1 (64-bit) Wayland
I've followed:
https://fcitx-im.org/wiki/Setup_Fcitx_5
https://wiki.archlinux.org/title/Localization/Japanese
https://wiki.archlinux.org/title/Mozc
as well as several user tutorials/forum posts
I've installed all of the fcitx and mozc packages.
I've enabled fcitx5 in KDE system settings and added a environment.d folder with the im.conf file.
Fcitx is showing up in the system tray, with "EN" and a kanji symbol. (I'm hoping to learn Japanese, I don't know it yet)
I can switch between the two by clicking the system tray, but the keybind I set will not work. (Indicating a deeper issue)
When I select the mozc input method, typing into any program just inserts English characters.
I also get this error whenever I log in:
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 Any pointers would be helpful here.
Thank you.
Last edited by Sushi_Samurai (2025-12-01 16:40:25)
Offline
You may also need to disable tools that launches input method, such as
You're most likely explicitly launching fcitx5 somehow, notably this is WRONG.
Offline
I didn't enable the "XDG Autostart" in my system. I checked the folder and it only has Yakuake (Drop down terminal)
Under the System Settings > Virtual Keyboard I have both Fcitx 5 and Fcitx 5 Wayland Launcher (Experimental) I've tried both and haven't seen a change between them.
Offline
There's actually a default /etc/xdg/autostart/org.fcitx.Fcitx5.desktop and a /usr/share/dbus-1/services/org.fcitx.Fcitx5.service dbus activation.
Try to remove /etc/xdg/autostart/org.fcitx.Fcitx5.desktop first to see whether it's coming from there.
Offline
Removing /etc/xdg/autostart/org.fcitx.Fcitx5.desktop causes fcitx to no longer start in the system tray. So it seems like that's where its coming from
Offline
Some progress. When I disabled /etc/xdg/autostart/org.fcitx.Fcitx5.desktop fcitx will no longer automatically start. BUT, when manually started I'm able to type Kanji as expected.
Now I just need to get fcitx to start via the KWin manager.
Offline
https://wiki.archlinux.org/title/Fcitx5#KDE_Plasma does not work??
Offline
Nope, I have it enabled in my settings but it won't auto-start. I've tried both of the options I have and neither of them have worked.
Offline
If the IME disappears, check whether the "On-Screen Keyboard" is deactivated.
Anything in the journal about the failure to launch fcitx5?
Offline
I looked through the Journal and no mention of fcitx, fcitx5 or mozc. There were quite a few dbus errors, but none seemed related.
Also, when I open the settings to the 'Input Manager' page, I'm able to use kanji for a bit. But at some point it fails and becomes unusable until I restart.
Offline
Also, when I open the settings to the 'Input Manager' page, I'm able to use kanji for a bit. But at some point it fails and becomes unusable until I restart.
If the IME disappears, check whether the "On-Screen Keyboard" is deactivated.
Otherwise, does fcitx5 crash?
https://wiki.archlinux.org/title/Core_d … _core_dump
Or at least: do you have an fcitx5 process as long as it works but no longer when it doesn't?
There were quite a few dbus errors, but none seemed related.
dbus-broker complaining that foo isn't named after bar is typically uncritical, but in doubt post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st*after* losing fcitx5
Offline
Happy Thanksgiving if you care about that.
Here is the journal? https://0x0.st/K4Bp.txt (I'm not sure if that works or If I'm an idiot)
Offline
Journla is ~5 minutes, the only signs of fcitx5 are from systemsettings:
Nov 27 09:26:32 arch systemsettings[4944]: E0000 00:00:1764260792.158888 4944 fcitx_key_event_handler.cc:123] Translate failed
Nov 27 09:26:32 arch systemsettings[4944]: E0000 00:00:1764260792.182848 4944 fcitx_key_event_handler.cc:123] Translate failed
Nov 27 09:26:33 arch systemsettings[4944]: I2025-11-27 09:26:33.426212 waylandmodule.cpp:641] GTK_IM_MODULE=fcitx
Nov 27 09:26:33 arch systemsettings[4944]: I2025-11-27 09:26:33.426218 waylandmodule.cpp:642] QT_IM_MODULE=fcitx
Nov 27 09:26:37 arch systemsettings[4944]: E0000 00:00:1764260797.255012 4944 fcitx_key_event_handler.cc:123] Translate failed
Nov 27 09:26:38 arch systemsettings[4944]: E0000 00:00:1764260798.783014 4944 fcitx_key_event_handler.cc:123] Translate failed
Nov 27 09:26:38 arch systemsettings[4944]: E0000 00:00:1764260798.823014 4944 fcitx_key_event_handler.cc:123] Translate failed
Nov 27 09:26:45 arch systemsettings[4944]: E0000 00:00:1764260805.503208 4944 fcitx_key_event_handler.cc:123] Translate failedIs there ever an fcitx5 process running?
Because it looks like the two variables are set?
=> See https://wiki.archlinux.org/title/Fcitx5 … e_problems - you don't want that on wayland.
fcitx5 also comes w/
fcitx5-diagnosethat can probably detect some standard setup problems other than those.
Offline
Well, I "fixed" it.
I re-installed my whole arch system. Now it boots on startup and works the entire time. The "Fcitx should be launched by KWin under KDE Wayland" still pops up every time I log in (I disabled it a this point) but it works and I'm good with that.
Thanks for all of your help seth!
Offline