Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GUI launched from wsl.exe does not respect locale settings #12151

Open
1 of 2 tasks
brianmaher84 opened this issue Oct 10, 2024 · 1 comment
Open
1 of 2 tasks

GUI launched from wsl.exe does not respect locale settings #12151

brianmaher84 opened this issue Oct 10, 2024 · 1 comment

Comments

@brianmaher84
Copy link

Windows Version

Microsoft Windows [Version 10.0.19045.4894]

WSL Version

WSL version: 2.3.24.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 20.04

Other Software

kitty 0.36.4
terminator 1.91

Repro Steps

It happens with both kitty and terminator terminals so I believe it is a wsl.exe issue that this occurs.

For example run the below command from windows shortcut to launch the terminal
C:\Windows\System32\wsl.exe -- /opt/kitty/bin/kitty --detach

The keyboard layout reverts to en_US even though the Windows system is set to en_IE and I exported every environment variable in my bashrc to try to force en_IE.

export LC_ALL=en_IE.UTF-8
export LANG=en_IE
export LC_CTYPE=en_IE.UTF-8

I've removed en_US from the Ubuntu and it still occurs.
locale -a
C
C.UTF-8
en_IE
en_IE@euro
en_IE.iso88591
en_IE.iso885915@euro
en_IE.utf8
POSIX

Expected Behavior

When I launch the terminal from wsl.exe, the locale should be respected by the application launched.

Actual Behavior

It launches as en_US no matter what locale I set.

Diagnostic Logs

No response

Copy link

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 [email protected] 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:

Closed similar issues:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant