Open pleappleappleap opened 1 year ago
This behavior renders X11 apps unusable.
Same problem on another Windows build. I confirm xterm is unusable, but it doesn't appear to affect all X11 apps. For example emacs 29.09 X11 build (guix build running on top of debian 12) seems fine.
Versions: WSL: WSL version: 1.2.5.0 Kernel version: 5.15.90.1 WSLg version: 1.0.51 MSRDC version: 1.2.3770 Direct3D version: 1.608.2-61064218 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.3324
I am ... orving ... observing (not joking: I am not fast at typing, and have to type like a snail to avoid this issue) the same problem when starting a WSL session in the Windows Terminal. The "kicker" is that the "illness" propagates to MSYS64 consoles and even browseees ... I mean "browser's" forms, as is the case RIGHT HERE! It is October 4, 2024 and this issue started appearing only a few days ago - more than a year after the last comment. (puzzled)
Two cents: I am only 50% this is WSL related: it feels like bad handling of keyboards interrupts. Maybe the wireless keyboard driver is misbehaving, because the batteries are fresh, but the illness appears to become really bad when WSL is active. It's driving me crazy and forcing me to reboot to alleviate the problem. Hoping for a miracle cure.
Looking at (similar) issue 1140 now - https://github.com/microsoft/wslg/issues/1140
Windows build number:
25393.1
Your Distribution version:
22.04
Your WSL versions:
Steps to reproduce:
I've verified the problem does *not occur in a console window. It only happens in X.
WSL logs:
No response
WSL dumps:
No response
Expected behavior:
No response
Actual behavior:
Here is an example of something I see all the time:
The missing spaces and letters were typed. The repeated "e" characters were not typed.