search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.24k stars 811 forks source link

WSLg crash after disconnecting monitor #11938

Closed St0nefish closed 2 weeks ago

St0nefish commented 3 weeks ago

Windows Version

10.0.22631.4037

WSL Version

2.3.14.0

Are you using WSL 1 or WSL 2?

Kernel Version

6.6.36.3-microsoft-standard-WSL2

Distro Version

Ubuntu 22.04

Other Software

IntelliJ IDEA Ultimate 2024.2.0.1 Docker 27.0.1

Repro Steps

I have a KVM connected to my home desktop and my work laptop. WSL is running on my work laptop with docker running the software I am developing and IntelliJ for dev work (via WSLg).

If I swap the KVM over to my desktop at any point while WSL is active then IDEA hangs and I am entirely unable to interact with it. If I kill it then it will not boot back up. If I close out IDEA prior to swapping the KVM then it just refuses to start.

I have only been able to resolve this by running wsl --shutdown in powershell then restarting the WSL instance entirely (including a full reboot of our docker cluster)

note: this was not happening on my previous version, but I have been part of the trial group for our internal WSL usage at work, so I typically update to early access builds. this seems to have been introduced sometime between 2.3.11 and 1.3.14. going by release notes mentioning an update to WSLg I'm going to guess it was likely 2.3.14

Expected Behavior

WSLg should not hang and require a reboot after swapping KVM inputs. I suspect this is due to changing the monitor config (external ones disconnect and everything moves to laptop's built-in screen)

Actual Behavior

all WSLg applications refuse to start until I shutdown the guest instance and restart it

Diagnostic Logs

No response

github-actions[bot] commented 3 weeks ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) 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:

Closed similar issues:

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

microsoft-github-policy-service[bot] commented 2 weeks ago

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!