Aurora IBus Wayland doesn't work in Chrome

[Haowen_Liu]

After installing Aurora, I installed IBus Wayland through Settings → Keyboard → Virtual Keyboard. After rebooting, IBus works fine in Libre Office and Firefox but doesn’t work within Chrome (flatpak). Anyone else seen that? Maybe there’s an extra flatpak permission I need to give to Chrome?

[mel226]

Since you’re on Aurora (KDE), can you try running this via the terminal: flatpak run org.chromium.Chromium --enable-wayland-ime --gtk-version=4 and see if it works then? (If --gtk-version=4 doesn’t work, maybe try --gtk4). If it works, you can add them to the Chromium config file, like so:

~/.var/app/org.chromium.Chromium/config 
> cat chromium-flags.conf
## enable wayland & hardware acceleration
--ozone-platform-hint=auto
--enable-features=VaapiVideoDecodeLinuxGL,WebRTCPipeWireCapturer
## input method
--enable-wayland-ime
--gtk-version=4

If it doesn’t work, you might want to try Fcitx5 instead of ibus. According to this Fcitx5 input switching should work fine with Chromium (and most likely Electron apps) if you’re using KDE. (It doesn’t work yet in GNOME, unfortunately).

[Haowen_Liu]

I see! I tried both but unfortunately none is working, quite unfortunately.

But my god! I tried fcitx5 and it works like a charm. It also integrates much nicely, and has a panel much more coherent with the KDE design language. Wow! It works so well that I almost think that should be what Aurora installs by default, not IBus

Anyway, thank you!

[mel226]

Glad to hear that! As far as I know Fcitx5 should be the default input method framework in KDE, I wonder if this is not the case for Aurora or Fedora at large? If so, @j0rge, maybe this is worth exploring

[Haowen_Liu]

I’d much rather not have to overlay packages, for that matter. But I also don’t see myself breaking the system because I installed fcitx

[j0rge]

Someone needs to file an issue and start making recommendations, I don’t know much about KDE so it needs to be in GitHub so others can see it (bluein repo):

How to file issues

While we try to help people as much as we can, we prefer that issues are triaged through GitHub so they can be tracked and labelled properly. Here’s a quick guide. If you’ve been redirected here it means one of us wants to track this in GitHub. Don’t worry, you didn’t mess up, we just need to put it in the system. This forum and GitHub support markdown formatting, so usually it’s just a matter of copying and pasting it into GitHub. Read the GitHub Quickstart Quick tips One issue per problem…

[Haowen_Liu]

Install fcitx5 on Aurora by default

[zwintabris]

I use Aurora, and I also need to use input methods. I use Fcitx 5 on Flathub and it solved all my input needs.

A few things to note:

1. A system level input method framwork (can be fcitx or ibus) is required for the Fcitx flatpak to integrate with your desktop environment. Since Aurora and Bluefin have ibus in their images, this dependency is already covered.

2. Specific input methods come as addons of Fcitx on Flathub. For now, very few addons are listed on flathub. You may try to look for the languages you need in Fcitx’s own flatpak repository if they’re not listed on Flathub.

flatpak remote-add --user --if-not-exists fcitx5-unstable https://flatpak.fcitx-im.org/unstable-repo/fcitx5-unstable.flatpakrepo

3. You have to let Plasma autostart Fcitx flatpak. This can be done in Plasma System Settings GUI.

Now you should have a working Fcitx input method without installing any layered packages.

If you you want to use fcitx for the GUI apps in a distrobox image, then you need to install fcitx5 package in that distro. The Fcitx from flatpak can magically function in these apps if you have fcitx5 installed in the container distro. Not all applications work though. Mullvad in an Ubuntu container does not take input methods, but Proton Pass does.