Due to the newest Nvidia 555 drivers making Firefox straight up not work for me (it crashes within seconds), and running it on XWayland making the performance much worse/introducing some weird graphics behavior, I have to use either Chromium or Brave until this somehow gets fixed.
Sadly, I also have performance problems with both of them when running them on XWayland, while by the other hand, running them natively just makes ibus/fcitx5 input methods not work inside of them (I tried both input methods).
However, digging online, it seems there is a way to make it work, although I couldn’t do it: running, say, Chromium with
doesn’t work. Apparently, you have to make it use gtk4 since there is a problem with it using gtk3 (?), I don’t know. Same for Brave, even though I only have the flatpak version of it, which might be the issue.
So, is it really just impossible, or am I missing something?
It is impossible to do it with Ibus or GNOME, but it is working now with fcitx5 and KDE Plasma 6 if configured correctly. I use other applications based on Electron like Obisidian (which is a Flatpak app), and have no issue with using fcitx5.
The only setup needed on system side is to set virtual keyboard to Fcitx 5 Wayland launcher, so you need to install kcm-fcitx5 in addition to language addons.
So, just out of curiosity: where is im-chooser setting the IM_MODULES variables? I remember it complains when you set the virtual keyboard thing under KDE Plasma, but I just could never find where those were set. It wasn’t under /etc/environment or any of the other expected paths, so I just ignored this warning last time I tried it.
I think it’s because Mutter is using text-input-v3 only, while Kwin uses both text-input-v2 and text-input-v3. Apparently, this causes problems with Chromium specifically. I tested yesterday with the Brave flatpak on KDE Plasma VM and it worked.