microsoft/WSL

CTRL + key does not work properly using Brazilian Portuguese keyboard layout

LuisHDantas opened this issue · 5 comments

LuisHDantas commented

Windows Version

Microsoft Windows [versão 10.0.22631.3447]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Ubuntu 22.04

Other Software

Discovered the problem while trying to use Neovim, but it happens anywhere in WSL.

Repro Steps

Pressing CTRL-] using BR keyboard layout results in "^\". Pressing ']' key without CTRL works properly, but it CTRL is pressed it thinks I am pressing '', which is the key that should be in that place if I used a US layout.

Expected Behavior

CTRL - ] should give me ^]

Actual Behavior

CTRL - ] gives me ^\

Diagnostic Logs

No response

github-actions commented

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 scipt will output the path of the log file once done.

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!

Closed similar issues:

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

LuisHDantas commented

Basically, I believe it is considering the US layout instead of the BR layout when trying to use shortcuts that require 2 or more keys.

OneBlue commented

Thank you @LuisHDantas. Is this in a terminal app, or in a GUI app that you see this ?

LuisHDantas commented

Thank you @LuisHDantas. Is this in a terminal app, or in a GUI app that you see this ?

I have not tried a GUI app, but I can say that it happens anywhere in the terminal (Neovim, or just the command line). I have tested with "showkey -a" and it gives me the wrong output that I mentioned above as well.

OneBlue commented

Ok thank you. In this case this means that the issue comes from your terminal. If you're using Windows Terminal, I'd recommend opening an issue there.

Closing since the issue isn't coming from WSL.