Arch Linux User Repository

https://gitlab.manjaro.org/packages/extra/manjaro-asian-input-support/

@MatrixC7

Fcitx5 has been updated and the problems I encountered earlier, caused by setting environment variables, may have improved. Nevertheless, the fact remains that Fcitx5 displays a message at startup in the KDE+Wayland environment, prompting the user to remove GTK_IM_MODULE and QT_IM_MODULE. You should therefore exchange your views with the developers and maintainers of Fcitx5 itself. If you think that my stance of following it is wrong, then you should create your own package and undertake to include support for those who use your package. That would be a practical solution.

It is not constructive to ignore my previous posts, specifically the cases where I have encountered trouble with setting environment variables, and to keep pointing out one-sidedly that my choices are wrong without also telling me what environment you are using. This is because even if You didn't encounter any problems in your environment, it is a fact that I did in my old environment.

As stated in the Fcitx5 startup message, it is recommended to use the Kwin VitrualKeyboard to start the Fcitx5 Wayland Launcher. That would still be the message from the developers. If you disagree with it, you should tell the Fcitx5 developers and maintainers.

You are asking me to do something different from the configuration recommended by the Fcitx5 developers, and I don't think it is a good decision for me to take you at your word. Therefore, I recommend that you create your own package and maintain it yourself. By doing so, the AUR can fulfil the purpose for which it exists.

@MatrixC7

This package is based on manjaro's configuration. manjaro's Kde environment has the kwin virtual keyboard enabled by default. fcitx5 also recommends running with the kwin virtual keyboard, as explained in the previous URL. It also displays a message recommending it. Since you do not describe your environment, I am assuming that you are using kde with wayland, but not with kwin virtual keyboard? In other words, you are using it in a way that is not recommended by fcitx5?

Your insistence that the old setup is fine ignores my previous posts. snap, flatpak, and aur are applications that are managed externally by the distribution, and the input method may not launch when using common applications in the repositories managed by the distribution, such as firefox. This is why the configuration has been changed. In other words, in wayland, you cannot use fcitx5, etc. for language input of multibyte characters in common applications with the old configuration. If your environment is different from mine and you prefer the old configuration, you should make a new aur package for yourself. That would be the best and easiest way to aur. I have installed and tried multiple environments and have come to the conclusion I have now. I am not a psychic, so, Since you do not describe your environment, I have no way of ascertaining why you are ignoring my previous posts and making such claims.

Nearly every application with GUI installed via the AUR requires modifications to the environment settings. Why not simply utilize the older version? Your approach to modify the file seems nonsensical, as it merely introduces additional complications for the user when the older version has no issues whatsoever.

Edit: I have uninstalled the package and manually set env var in /etc/environment. :) To future possible readers: Though fcitx5 wiki says on KDE+Wayland only XMODIFIERS=@im=fcitx is enough and GTK_IM_MODULE & QT_IM_MODULE are unnecessary, but sometimes without GTK_IM_MODULE & QT_IM_MODULE the input box of IME would be out of place and setting vars could fix it. Remember to not blind-believe wiki but respect the reality!

I encountered the same problem when I tried the snap version of Discord.
If you are using the snap version of Discord, please try the following method.

cp /var/lib/snapd/desktop/applications/discord_discord.desktop ~/.local/share/applications/
sed -i "s|Exec=\(.*\)|Exec=env GTK_IM_MODULE=fcitx env QT_IM_MODULE=fcitx env XMODIFIERS=@im=fcitx \1|" ~/.local/share/applications/discord_discord.desktop 
cat ~/.local/share/applications/discord_discord.desktop 

[Desktop Entry]
X-SnapInstanceName=discord
Name=Discord
StartupWMClass=discord
Comment=All-in-one voice and text chat for gamers that's free, secure, and works on both your desktop and phone.
GenericName=Internet Messenger
X-SnapAppName=discord
Exec=env GTK_IM_MODULE=fcitx env QT_IM_MODULE=fcitx env XMODIFIERS=@im=fcitx env BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/discord_discord.desktop /var/lib/snapd/snap/bin/discord
Icon=/var/lib/snapd/snap/discord/228/meta/gui/icon.png
Type=Application
Categories=Network;InstantMessaging;

In my environment, this method solved the problem.

Just to be sure.
Do you have fcitx5-wayland set to start from virtualkeyboard?
You have not set QT_IM_MODULE and GTK_IM_MODULE in the environment variable settings, have you?
Are you re-logging in to reflect those setting changes?

I'm using Manjaro, I tried Discord in KDE Wayland and GNOME Wayland, no input position (cursor position) problems. flatpak version of Discord was older version, but no problems there either.

Are there any problems in your environment with older or earlier settings, such as Firefox or Kwrite, the editor provided by KDE?

Also, is your OS a bare-bones(plane) ArchLinux environment? Or is it a derivative of Arch such as Endevour or Chacy?

Setting e.g. GTK_IM_MODULE causes conflicting settings, which can get you in trouble with other applications.
It may be necessary to adjust the start-up on the application side, like google-chrome.

Which version of Discord are you using? Official repository or flatpak, snap?
I will check later.

Have you seen the pic? All keyboard settings are already shown and been there and only returning to old version could fix the problem.