Yes, I have the same issue. I think it’s because the fcitx version in Ubuntu 24.04 LTS isn’t new enough, while Plasma 6.7.x has dropped the old Wayland input protocol. Wayland has been around for years but still feels like a toy — I don’t think there’s any straightforward fix.
On the bug tracker, someone suggested replacing fcitx with the Flatpak version. If you have the means, you could give that a try.
However, my system can’t access any sites outside the DEB mirror sources, so I have to stick with the old Fcitx and hope that Neon upgrades to Ubuntu 26.04 LTS sooner rather than later.
As a workaround, here’s what I’m currently doing (for reference only):
In Settings → Keyboard → Virtual Keyboard, select Fcitx 5 Wayland Launcher. When starting up, Fcitx will complain that you should choose Fcitx 5 instead, but just ignore that.
For all Chromium-based applications, add GDK_BACKEND=x11 GTK_IM_MODULE=fcitx5 XMODIFIERS=@im=fcitx5 to their environment variables, and add --ozone-platform=x11 to their startup parameters, forcing them to run under XWayland as a temporary workaround.
I don’t have any GNOME software on my system, so I can’t comment on that situation.