-
Notifications
You must be signed in to change notification settings - Fork 1.3k
wslinfo --msal-proxy-path hangs #12714
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
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
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 |
Diagnostic information
|
Thank you for reporting this @mdbooth. Does this happen all the time, even after a WSL restart ? |
Yes |
Ok I think I know why. You had Can you try again after upgrading to 2.5.4 ? |
Interesting, that should still not hang querying of the environment variable. I will take a look. |
@OneBlue is right, but there is still a small issue in this path. I will fix this as a follow-up. |
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue. Thank you! |
Uh oh!
There was an error while loading. Please reload this page.
Windows Version
Microsoft Windows [Version 10.0.26100.3476]
WSL Version
2.4.12.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.167.4-1
Distro Version
Fedora 41
Other Software
No response
Repro Steps
wslinfo --msal-proxy-path
Expected Behavior
Not sure, tbh, but rocminfo runs it and presumably it doesn't expect it to hang. I see an identical report of the issue I'm hitting here: ROCm/ROCm#4281
Actual Behavior
It hangs. It is also not possible to kill it from the terminal. I can kill it from another terminal, then close and re-attach to my tmux session to resume, but I can't continue from the same terminal even after killing it. Whatever death this dies is also not very nice to the terminal.
Diagnostic Logs
Running it in strace suggests it hangs expecting a response from
/run/WSL/471_interop
which it never gets.The text was updated successfully, but these errors were encountered: