You are not logged in.

#1 2025-05-12 10:25:55

yamcake3821
Member
Registered: 2024-10-25
Posts: 16

Problem With Fcitx5

So, I have a problem with Fcitx5 lately, which is I can type normally (in chinese) on a certain window but I couldn't with the other, the video is pretty self explanatory: https://drive.google.com/file/d/1eOshVz … sp=sharing

Oh yeah, and I use Hyprland.
Thanks.

Offline

#2 2025-05-12 13:26:25

seth
Member
Registered: 2012-09-03
Posts: 63,543

Re: Problem With Fcitx5

the video is pretty self explanatory

And likely meaningless, https://bbs.archlinux.org/viewtopic.php?id=57855

Wild guess, does it hinge on xwayland?
Also see https://wiki.archlinux.org/title/Fcitx5#Wayland

Offline

#3 Yesterday 11:26:41

yamcake3821
Member
Registered: 2024-10-25
Posts: 16

Re: Problem With Fcitx5

My apologies, I read the "How to ask questions the smart way" and came back, here's my journal.

http://0x0.st/8v_M.txt

Offline

#4 Yesterday 19:43:32

seth
Member
Registered: 2012-09-03
Posts: 63,543

Re: Problem With Fcitx5

How will the journal be helpful here?

Details on the affected client(s) will be more useful:
https://wiki.archlinux.org/title/Waylan … plications
https://wiki.archlinux.org/title/Fcitx5 … e_problems

Offline

#5 Yesterday 20:42:13

frostschutz
Member
Registered: 2013-11-15
Posts: 1,542

Re: Problem With Fcitx5

I have the same issue with Chromium (running in wayland gtk4 mode, under swaywm). As long as there is a single window, fcitx works fine. Multiple windows (side by side, or on different virtual desktops), then IME only works for one of them.

No such issue in firefox, terminal, etc. so it should be something chromium specific I guess.

Offline

#6 Yesterday 22:01:52

seth
Member
Registered: 2012-09-03
Posts: 63,543

Re: Problem With Fcitx5

Tried any of the "--wayland-text-input-version=3" or --en/disable-wayland-ime for chromium/electron?

Offline

#7 Today 00:53:25

frostschutz
Member
Registered: 2013-11-15
Posts: 1,542

Re: Problem With Fcitx5

Okay. Well. Disabling wayland text input version 3 makes IME work in multiple windows. That's great. But then AltGr key stops working, so I can't type ASCII anymore. So it's useless for me. Maybe it will help OP...

I'm tuning out chromium anyway. Why is every browser buggy, sigh hmm

Offline

#8 Today 05:20:47

seth
Member
Registered: 2012-09-03
Posts: 63,543

Re: Problem With Fcitx5

https://issues.chromium.org/issues/40239118#comment13
What's your current set of chromium flags to address this (found an older post of yours concerning this)

Why is every browser buggy

… becaues html5 was, ultimately, a mistake.

Offline

#9 Today 07:49:55

frostschutz
Member
Registered: 2013-11-15
Posts: 1,542

Re: Problem With Fcitx5

I don't have flags other than setting ozone/wayland and gtk version. The input version 3 was used by default (apparently).

--enable-features=UseOzonePlatform
--ozone-platform=wayland
--gtk-version=4

And yeah, the AltGr issue is a years old bug with Chromium + GTK 4. However IME does not work at all without it. So I switched to GTK 4 again recently and was surprised to find that AltGr was fixed, but apparently that is related to the input protocol version 3 somehow. And this works fine, except IME now only works in a single window. Which I didn't even realize before this thread appeared - I don't have that many tabs open so a single window is usually sufficient.

Maybe its something benign like getting the window id wrong or something. But I don't even know where to start looking in the source code, and I'm switching back to firefox based browsers anyway, so... someone else have to debug it ;-)

Last edited by frostschutz (Today 07:50:14)

Offline

Board footer

Powered by FluxBB