Keyboard input not working altogether

[ktufekcic]

Windows Version

Microsoft Windows [Version 10.0.22631.4037]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 22.04

Other Software

All GUI apps running through WSLg
WSLg version: 1.0.61

Also attempted with prerelease version of WSL: 2.3.17.0 and WSLg: 1.0.64

Repro Steps

The issue is pretty much identical to this one: #955
Unfortunately I wasn't able to open an issue in WSLg directly for some reason, so I had to go here, sorry about that.

I went through the steps mentioned in the link there, as well as a whole bunch of other articles online, but nothing fixed it.
I can use function keys and CTRL C/V/X/A/etc for certain actions, but I can't actually type any character.s One unique situation here is that this instance of Windows is running in an Azure VM, and I'm accessing it (usually) from Linux with Hyprland, however, I tried accessing it from Windows (multiple machines with multiple keyboard layouts), I tried changing Windows keyboard layouts, Linux locales, reconfiguring locales, setting a symlink to Windows' fonts, nothing seemed to work. Any and all help is extremely appreciated as this is a very important business usecase for which WSLg is effectively the last hope.

Regarding the reproduction steps, I'm not sure if this will be easy to reproduce, as I mentioned this is a VM, I haven't tested to see if I can replicate this behavior locally in kvm or something, but please let me know if that would help.

Install any GUI app (I tried JetBrains Toolbox/IntellliJ and Firefox) and launch it
Try to use keyboard input

Expected Behavior

Keyboard input is detected and works as expected

Actual Behavior

There is no keyboard input detected, the text fields remain blank

Diagnostic Logs

WslLogs-2024-09-11_15-40-19.zip

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• Keyboard in WSL2 Doesn't Follow Windows Input Language, GUI Applications Not Adhering to Set Default (#11054), similarity score: 0.80
• Wrong or no keyboard input into X11 applications via remote desktop (#9571), similarity score: 0.75
• in GUI applications installed in WSL, the keyboard layout does not switch to another language (#9954), similarity score: 0.71

Closed similar issues:

• High keyboard latency when running wsl (#9711), similarity score: 0.71
• Windows touch keyboard - special characters not working (#7005), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[github-actions]

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/16963814/WslLogs-2024-09-11_15-40-19.zip
.wslconfig found
	Custom kernel command line found: 'vsyscall=emulate'
Detected appx version: 2.3.17.0

[ktufekcic]

WslLogs-2024-09-11_15-40-19.zip

[github-actions]

Diagnostic information

.wslconfig found
	Custom kernel command line found: 'vsyscall=emulate'
Detected appx version: 2.3.17.0

[ktufekcic]

I will close this issue as I found a workaround, and I don't think the issue has anything to do with WSLg or WSL.
For anyone else facing similar issues, the root cause isn't Windows itself or the fact that it's a VM (at least not in my case), but the web browser. As I mentioned this is an Azure VM, and I was accessing it via browser, since the remote desktop app isn't natively available on Arch Linux. After doing a test, it seems that when using the app everything works just fine, so while it may be worth investigating how to fix this on a browser level, it's unnecessary to leave this ticket here.