https://bugs.kde.org/show_bug.cgi?id=506095
Weng Xuetian <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|UPSTREAM |--- CC| |[email protected] Ever confirmed|0 |1 --- Comment #20 from Weng Xuetian <[email protected]> --- Hi, fcitx dev here. No, such issue can only be triggered by kwin. Here's the things: 1. while there's on/off from user point of view, it's always "on" in the sense whether the key event flows to input method. 2. The behavior, as shown in video, seems to be kwin send zwp_input_method.activate() to fcitx and fcitx placed a keyboard grab. While this should be managed together with the keyboard focus, it seems (at least from the video, since I didn't reproduce it, maybe it requires certain app?) that kwin fails send deactivate input method when xwayland window get focused. I think the reporter probably want to open a terminal and run fcitx5 with WAYLAND_DEBUG=1 fcitx5 and focus on the zwp_input_method , so we could see the interaction between kwin & fcitx & window focus change. 1. quit/kill all fcitx5 process 2. Run `WAYLAND_DEBUG=1 fcitx5 2>&1 | grep zwp_input_method` in a terminal, keep it visible while recording 3. Select Fcitx5 Wayland launcher (instead of fcitx5) in systemsettings, so it can use the fcitx5 started by (2) instead of starting a new one 4. Try to reproduce the issue your describe. When you focus into a non wayland app, if it's normal, you should see: ``` [ 681741.584] {Default Queue} zwp_input_method_v1#14.deactivate(zwp_input_method_context_v1#4278190081) ``` -- You are receiving this mail because: You are watching all bug changes.
