"stuck" keys on xwayland

[c0h2r]

description

So, I have 2 xwayland windows (one is a terminal, and another one doesn't really matter). Then I exit the shell with <C-d> which closes the terminal, and 'd' gets kinda "stuck" (for the lack of a better word in my vocab) for all other xwayland windows I focus after that and until I press something else.

demo

untitled.mp4

Here I show the behavior on 2 instances of wezterm with enable_wayland = false specified in the config, but the same also goes for 2 sts or wezterm and brave (without the env vars that tell chromium stuff to run natively)

details

OS: NixOS
Cosmic-comp commit: probably 9cb1adb (i.e. the one in https://github.com/lilyinstarlight/nixos-cosmic/blob/d9f0cdbc53b3a602e9faea5b2efbe7804639cb3c/pkgs/cosmic-comp/package.nix)

[Drakulix]

Oh that is a fun bug... thanks for reporting.

Initial guess what is causing this issue (more a note to myself): Application closes, cosmic-comp revokes focus from the window, we don't have a valid target to send keyboard events to, Xwayland never gets wl_keyboard::key-event for the released key. (It should however get the keyboard::leave event, but most likely doesn't do anything with it.)

Needs some more in-depth debugging and probably some workaround for release-events with long-running clients.

[WatchMkr]

I'm unable to reproduce this bug. Can it be closed?

[hgaiser]

I still have this issue on alpha 5. If I run glxgears and exit by pressing Escape, then run glxgears again it closes immediately because it receives an Escape key event.

The same thing seems to happen in any XWayland application that can be closed by a key event. Ie. if I write an OpenCV image viewing application and add an option to exit through some key event, the same thing happens.

Small disclaimer: it seems to be XWayland applications only, but I'm not 100% sure. For example if I try to fix it by going to a Qt application, hit the stuck key, then glxgears still exits immediately. However what puzzles me is that I configured electron to run under Wayland, not XWayland 🤷

Let me know if you have some pointers in the code where I can put some debugging code to help resolve this issue.

[leviport]

It can also be recreated with Chromium. If I close Chromium with Super + Q, relaunching it causes it to close immediately.

Another way to show the bug is to hold a letter key down while clicking the X button on the Chromium window. Then (with the key released) I can open Chromium again, and the URL bar starts filling up with the letter I was previously holding until I hit some keys again to send it new key release events.

[hgaiser]

@WatchMkr just curious if you've managed to reproduce the issue or if you need more information. I see the alpha 7 milestone has been added which is fine for me. It's a minor annoyance to be honest, but it definitely still exists.