wslg
wslg copied to clipboard
microsoft
No keyboard input via remote desktop from Mac/iPad (Need support for Unicode input)
Version
Microsoft Windows [Version 10.0.19043.2364]
WSL Version
- [X] WSL 2
- [ ] WSL 1
Kernel Version
Linux version 5.15.79.1-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34.0.20200220) microsoft/WSL#1 SMP Wed Nov 23 01:01:46 UTC 2022
Distro Version
Debian GNU/Linux 11 (bullseye)
Other Software
X11-apps: xterm chromium MS Remote Desktop 10.8.0 (2032) macOS Ventura 13.2
Repro Steps
Connect via Microsoft Remote Destop to Windows-PC from MacOS Ventura 13.2. MS Remote Desktop App. Start wsl by command in a powershell and then xterm or chromium. Try to enter characters into the resulting xterm- or chromium windows. Return works, but any other character creates no response.
Expected Behavior
normal input of all characters into the xterm window or the chromium address field.
Actual Behavior
Result after hitting some characters and the return-key
No characters are shown, except the return key works in an X11 window
Diagnostic Logs
No response
/mnt/wslg/weston.log on a fresh started system with one xterm running.
@dh7adr, thanks, the log indicates you are using German keyboard layout, would you please check if German keyboard layout is used both Mac and the remote Windows-PC? Although even keyboard layout does not match, I believe alpha-numeric keys still should work as they share same scan code. So if you type any alpha-numeric key, say 'q' or 'w' to xterm, does it log any errors to weston.log? thanks!
[16:16:34.022] kbd_layout:0x407 kbd_type:0x4 kbd_subType:0x0 kbd_functionKeys:0xc
[16:16:34.022] convert_rdp_keyboard_to_xkb_rule_names: matching model=pc105 layout=de variant=(null) options=(null)
@dh7adr, while I don't have Mac, but I was able to reproduce the issue using remote desktop on iPad, I willl look into further, thank you for reporting the issue, thanks!
@dh7adr, you should be able to workaround this by using "Scancode" input from Connection menu, Keyboard mode, then check "Scancode". Please let us know how it goes, thanks!
Hello,
great! This works for me. Scancode is a good workaround.
I´m using the german keyboard layout at every computer. There are some differences between iMacs and PCs, but this is only an issue with some special shifted characters and functions.
Thanks,
Andreas
Scancode
Hi, is there a Scancode option on the Windows Remote Desktop Clinet on iPad？
or is there any way to input into WSLg on an iPad?
I have this same issue with RDP on an iPad. Also seems to affect the Hyper-V console.
Bump too… I’ve been watching this issue for a year, and right now my workaround is to VNC into a native Linux machine and execute xfreerdp from there. But that’s certainly annoying!
Just bumped up against this issue on iPad / WSLg. Is there any update / workaround available / in the works?
Hello, I too am hitting this when using the MS RDP Application. Where is this 'scancode' option and is there a more permenant fix in the works?
Is this a bug in the MS RDP App maybe?
I notice when running xev via WSLg, arrow keys, enter, escape, tab and backspace generate kb events but no alpha numeric keys do
