https://bugs.kde.org/show_bug.cgi?id=506095
--- Comment #3 from [email protected] --- Same issue. Also found that: - The issue occurs regardless of whether fcitx is started via "Fcitx5" or "Fcitx5 Wayland Launcher" in the "Virtual Keyboard" settings. - When the issue occurs, focus on a non-XWayland window (alacritty in my case), switch the input method back and forth, then refocus on the problematic XWayland window, the issue usually goes away. -- You are receiving this mail because: You are watching all bug changes.
