Arch Linux User Repository

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

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.

It is indeed confusing to call it a virtual keyboard, but even if you are using a physical keyboard, try starting fcitx5 from a virtual keyboard.
Start fcitx5 by go to "System settings" -> "(Mouse and )Keyboard" -> "Virtual keyboard" -> Select Fcitx 5 or Fcitx5 Wayland.

In the KDE Wayland environment, the Fcitx5 recommendation would be to boot from Kwin (VitrualKeyboard). This is because the information on the support wiki and in the warning window that Fcitx5 displays when setting environment variables says so. fcitx5-diagnose has probably not kept up with the handling of environment variables in KDE Wayland.

Yes I am using fcitx5 however not with virtual but physical keyboard. I have just taken a photo for you to show the problem as https://imgur.com/a/dcBcNrE.

@MatrixC7 Since you are using fcitx5-diagnose, you are using fcitx5, not fcitx, right?
Fcitx5 warns you not to set these environment variables if you have GTK_IM_MODULE and QT_IM_MODULE set in wayland.
The support wiki also says not to set them.
https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland#KDE_Plasma

• Environment variables:

  • Set XMODIFIERS=@im=fcitx for XWayland application
  • Start fcitx5 by go to "System settings" -> "Virtual keyboard" -> Select Fcitx 5
  • Do not set GTK_IM_MODULE & QT_IM_MODULE & SDL_IM_MODULE . You could unset GTK_IM_MODULE & QT_IM_MODULE by runing im-config and then selecting do not set any IM from im-config and use desktop default"
  • Run chromium/electron application with --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime

• Caveats:

  • Certain Gtk/Qt application that only works under X11 may still need to set GTK_IM_MODULE or QT_IM_MODULE for them individually.
  • If you set GTK_IM_MODULE/QT_IM_MODULE globally, you will hit this issue Candidate window is blinking under wayland with Fcitx 5

Are you running fcitx5-wayland from virtualkeyboard(KWin)?

In the latest version there still remains problems for both CN and JP input as I use. The place of the input would not be the place of cursor and as you do fcitx5-diagnose in konsole you would find it still lacks the env var for QT in KDE w/ wayland. Like before staying in the version 2021.09 e17561 fixes it for me. My environment is as below.

KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.13.2-arch1-1 (64-bit)
Graphics Platform: Wayland

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

@MatrixC7

Thanks for the report.
I have reverted only to the fcitx environment of KDE, as some environments did not allow Asian language input when environment variables were present.
In KDE(Wayland), only fcitx has the environment variable set.
Please use KWin VirtualKeyboard for both ibus and fcitx5 in KDE.

I installed and tried Google Chrome(AUR,deb package conversion).

GNOME(Wayland) No environment variables required.

KDE(Wayland) Some environment variables are required. Firefox, Kwrite, Konsole, etc. cannot start IME and input if GTK_IM_MODULE or QT_IM_MODULE is set. Therefore, only the other environment variables have been modified to be set. This modification was made because environment variable settings can be an obstacle.

If you are still having problems, please let me know your specific environment.

Please consider adding the following options to the wayland operation.
By adding this option, even when running Google Chrome in the AUR package with Wayland,
IME activation was performed and Japanese input was possible. For your reference.

google-chrome --enable-wayland-ime --ozone-platform-hint=auto --wayland-text-input-v3=enable

echo --enable-wayland-ime --ozone-platform-hint=auto --wayland-text-input-v3=enable|xargs -n1| tee -a $HOME/.config/chrome-flags.conf

If this does not bring up the IME, go to chrome://flags, set the flag ozone-platform-hint to auto, enable wayland-text-input-v3, and restart chrome.

references: (Japanese) https://zenn.dev/ikuya/articles/39b03d8485471f https://zenn.dev/compass/articles/e1f4c88e78b721