https://bugs.kde.org/show_bug.cgi?id=506095
ShwStone <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #12 from ShwStone <[email protected]> --- I can confirm that I have also encountered this issue with Fcitx5 in XWayland applications under a Wayland session. The core problem appears to be an input method desynchronization between the Wayland session and the XWayland server, as you've correctly pointed out. My specific experience closely mirrors the one described in the original report, but with a few additional details that may be helpful: The Trigger: I've found a consistent way to trigger this bug. When I switch the input focus from an XWayland window to a native Wayland window, activate the input method in the Wayland window, and then switch back to the XWayland window, the issue occurs. The Symptom: When I press `Ctrl+Space` to switch the input method in the XWayland window, the candidate box appears in the top-left corner of the screen, and I'm unable to type in Chinese. Affected Applications: This bug affects almost all my XWayland applications, including VSCode, QQ, and WeChat. While VSCode can run natively on Wayland, WeChat cannot, which makes this bug particularly disruptive for me. Workaround: The only reliable way I've found to temporarily fix the issue is to close the affected XWayland window and reopen it. Configuration: I've followed the input method configuration instructions from the Arch Linux wiki and tried various environment variables like `QT_IM_MODULE` and `QT_QPA_PLATFORM`, but none of them have resolved the problem. It's possible I've missed a minor configuration detail. A Strange Observation: The Fcitx5 candidate box border in the problematic XWayland windows seems much thinner than in the native Wayland windows. I'm not sure if this is relevant, but I haven't observed this on my other machine that isn't experiencing the bug. I have a second computer running Manjaro with the same software and configuration, and it did not exhibit this behavior. However, after upgrading its KDE packages (including KWin) from version 6.3.6 to 6.4.4, the bug was successfully reproduced, strongly suggesting a regression in a recent KWin update. I've attempted to downgrade packages like `kwin`, `kwin-x11`, and `aurorae` but ran into a black screen issue with SDDM. Any help would be appreciated. This seems to be a significant regression in a recent KDE update, and I'm very concerned about it since it affects essential applications like WeChat. I hope this provides more clarity and helps in narrowing down the cause of this frustrating bug. -- You are receiving this mail because: You are watching all bug changes.
