Fcitx forcefully activates Japanese input mode when I enter text to Konsole and Yakuake

[phanect]

I use fcitx5 (with a Japanese IME mozc) on KDE neon.

Recently, when I type a character on Konsole and Yakuake, the input mode is forcefully changed to Japanese Hiragana regardless of the input mode I used on the other apps.
I can switch back to English by pressing the key to deactivate the input method (Hankaku/Zenkaku key), but I have to press the key every time I open Yakuake and Konsole.

I took a screencast to show the current behavior. I never pressed keys to activate/deactivate/toggle the input method while I was taking this screencast.

https://www.youtube.com/watch?v=2VJHQWLtlFE

First, I set the input mode to English. I pressed the "a" key on Kate, and "a" is displayed in Kate as expected.
Next, I switched to Konsole, then I pressed "a" again. I expected "a" to be displayed as well, but Japanese "あ" is displayed instead. This means that the Japanese input method is enabled on Konsole.
At last, I went back to Kate and pressed "a", then "a" was displayed. This may imply that the input method mode is separately managed on Konsole.

I tried Electron apps (GitHub Desktop Linux) and GTK apps (Meld) instead of Kate, but the results were the same.

When I tried Google Chrome's address bar, the result was the same, but interestingly, when I tried with a text field in a website on Google Chrome, the behavior was a bit different:

1. Enter "a" on a website's text field on Google Chrome, then "a" is displayed.
2. Switch to Konsole and enter "a" again, then "a" is displayed. (expected)
3. Switch from Konsole to Yakuake and enter "a" again, then Japanese "あ" is displayed. (unexpected)

I'm not sure if this is a bug of fcitx5 or other software including Konsole, Yakuake, and Plasma, so I need help to find the cause.

This issue started to happen several weeks or months ago. It might have started after the Plasma 6.2 upgrade, but I might remember incorrectly. Sorry.

I have asked the same question on KDE Discuss, but couldn't find the cause and solution:

Fcitx forcefully activates Japanese input mode when I enter text to Konsole and Yakuake | KDE Discuss

My env:

• The OS/Distro I tested: KDE neon (all updates applied as of 2025/02/15 2:10 AM UTC)
• fcitx 5.1.7
• Plasma 6.3.0 with Wayland
• Konsole/Yakuake 24.12.2

Thanks in advance.

[misprogrammed]

Hello Phanect,

I think I might have a solution to your problem.

The method that worked for me uses the fcitx5-configtool package. Here is what I did:

I used htop to kill fcitx5. Then I set the virtual keyboard to fcitx, typed fcitx5-configtool into terminal and pressed return.

I was presented with the following window:

This setting tells what languages are the startup defaults for programs. I simply dragged Anthy into "off" and my Roman keyboard into "on".

I hope this helps.

[phanect]

Thanks!
I will check the configs.

[phanect]

Sorry for no response for long.
I finally got chance to try your solution, and it worked on my end by adding Keyboard - Japanese in addition to mozc.
Thank you for your assistance!

[misprogrammed]

どういたしまして。

[duckbytes]

Were you ever able to figure this out? I'm experiencing a similar issue except it seems to default to Japanese input on any new window.

I'll be typing with English keyboard, then press super to search and it'll default to hiragana. Or if I open another browser window, it'll also default to hiragana.

Strangely enough if I go back to the original browser window, it'll revert back to English.

It almost seems like it's saving the input method per window and defaulting to Japanese. I want it to only use one input and switch when I press ctrl+space.

[wengxt]

yakuake is in kinda a weird situation: it's window is gone from window manager when hidden. Comparing to other application, when minimized, the kwin's window management still report that the window exists.

Right now I don't really have a easy way to solve it: you can try to set the state to be shared, but that might not be what you want.

[wengxt]

actually no. fcitx still get yakuake, but seems due to window state it removes it. So it seems to be a chance to fix it.

[wengxt]

... actually I misread the log, the yakuake is indeed gone from plasma window management protocol, so fcitx think it's quit.

[phanect]

Sorry for no response for long.
I finally got chance to try @misprogrammed's solution, and it worked on my end by adding Keyboard - Japanese in addition to mozc.