Workaround for Gnome Text Edit, Chromium, etc on Wayland?

[HubKing]

It seems that FCITX5 does not work on Gnome Text Editor and all Chromium-based browsers if Wayland is enabled by setting Preferred Ozone platform to Auto in chrome://flags. The DE is Gnome 43.2, and I am using Wayland.

Is there any workaround?

[wengxt]

as for chrome ,you need --gtk-version=4 flag to make it able to use gtk4 im module.

For Gnome text editor it should work. What's your distro and how did you install gnome-text-editor? Did your distro split fcitx5-gtk in to a separate gtk4 package?

[HubKing]

It seems that not only on the text editor, but Fcitx is not working on any GTK4 app.

[wengxt]

Then you might didn't set GTK_IM_MODULE?

Can you paste the output of fcitx5-diagnose?

For chromium this works for me

GTK_IM_MODULE=fcitx chromium --enable-features=UseOzonePlatform --ozone-platform=wayland --gtk-version=4

[HubKing]

GTK_IM_MODULE=fcitx made no difference.

Here is the output of diagnostics: output.txt

[wengxt]

I saw gnome-text-editor is already connected to fcitx, so I think it should already work?

      IC [fc402107f14245bba3ba8b3978d797fb] program:gnome-text-editor frontend:dbus cap:4001000012 focus:0

Or it could be a hotkey conflict? Does "Ctrl + ;" show the fcitx clipboard in gnome-text-editor?

As for chromium, how did you install it?

I tried with chromium arch repo and from AUR both seems to be work for me.

[HubKing]

Chromium was from the official repository.

Ctrl+; worked. I was using "Windows + Space" as the only shortcut for changing language, so I added a weird combination like Ctrl+shift+I in addition, and that worked on both the text editor and Chromium. I do not know why Windows + Space works on GTK3 apps and other apps like FireFox, but not on GTK4 and Chromium.

[HubKing]

I did some more testing and it seems that Fcitx cannot get any combination of Windows key (or "Super" as Gnome calls it) shortcut on any GTK4 application. It can, however, get such shortcuts on GTK3/QT applications.

Is this a new limitation or a bug of GTK4, or is it because Fcitx is not handling the shortcuts correctly on GTK4 applications? If it is the former, I may report this to GTK developers.

[wengxt]

Yes, you're right. Seems gtk doesn't report native xkb modifier state anymore, but only it's virtual super key state, which fcitx doesn't recognize as super. Need to make some change to make it work.

Sorry I seems to misunderstood the actual issue, yeah, the modifier state of super is not correct in gtk4 ... let me check closer..

[wengxt]

Ok, two separate issues. Under gnome is exactly what I mentioned earlier. under kwin it's unclear to me, might be a gtk4 bug.

[wengxt]

Reported: https://gitlab.gnome.org/GNOME/gtk/-/issues/5476

Maybe you want to try ctrl+space as a workaround. (Personally I'd say "single right control" is another good candidate)

[wengxt]

Ah, I forget you're using gnome,

So with 469e849 it should work under gnome now.

[HubKing]

Thanks. So, it means that, in future releases, Win+Space would work for GTK4 apps with 469e849 ? The default key was Ctrl+Space, I think, but that key combination is used by many code editors to show auto-complete, so I had been using Win+Space. Alt+Space is used by the window menu, so I have added Shift+Space temporarily for GTK4 apps.