https://bugs.kde.org/show_bug.cgi?id=506095
--- Comment #25 from Weng Xuetian <[email protected]> --- https://github.com/samduanx/glossaries/raw/refs/heads/main/fcitx.mp4 https://github.com/wold9168/Pictures/blob/main/video/2025-09-18%2016-39-12.mp4 In the two videos here, what's abnormal is that, when using Xwayland application, the zwp_input_context is still active and fcitx is getting key events. Now I can relatively easy to reproduce this issue. https://bugs.kde.org/show_bug.cgi?id=506095#c23 Comment 23 gives a very useful clue. Here's the exact step: 1. open xterm, and minimize it. 2. Focus on to any text input client, e.g. kwrite. I tried firefox, not reproducing it. Maybe text-input-v2 client is more likely to reproduce.. 3. Use Alt+Tab to switch to xterm. 4. From fcitx side, it is getting zwp_input_context.activate, thus it placed a keyboard grab. For step 3, if xterm is not minimized and use mouse click to switch focus, the zwp_input_context.deactivate is correctly called, which shows that the "activate" in this bug is not intentional. The issue on kwin side is that "zwp_input_context.activate" shouldn't happen. -- You are receiving this mail because: You are watching all bug changes.
