microsoft / wslg

Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
MIT License
10.1k stars 304 forks source link

GUI apps freeze as soon as detecting network change #1108

Open castorfou opened 1 year ago

castorfou commented 1 year ago

Windows build number:

10.0.22621.0

Your Distribution version:

22.04

Your WSL versions:

Version WSL : 1.3.17.0 Version du noyau : 5.15.90.4-1 Version WSLg : 1.0.57 Version MSRDC : 1.2.4485 Version direct3D : 1.608.2-61064218 Version de DXCore : 10.0.25880.1000-230602-1350.main Version de Windows : 10.0.22621.2134

Steps to reproduce:

Here are the steps to illustrate the issue.

Connect laptop to wired network. Start WSL-ubuntu Launch X11 apps such as tilix Remove ethernet cable (host automatically switches to wifi) Instantly tilix window disappear Relaunch tilix from wsl prompt: 2 tilix windows appear but they are unresponsive (cannot get control, cannot move, cannot type into)

This is to illustrate the issue. A more frequent case would be a running wsl session, I close lid to move to another room and when opening lid my x11 apps are gone. I guess something is linked to network in that case as well. (suspend ?)

I am not sure it is linked to wslg not showing GUI (due to crash at rdprail-shell).

WSL logs:

wlog.log weston.log

WSL dumps:

I have one of 256M. Can upload if it can help

Expected behavior:

X11 apps to still be visible and responsive

Actual behavior:

X11 apps disappear and when re-run they appear but are unresponsive (frozen)

castorfou commented 1 year ago

here a small video to illustrate

https://github.com/microsoft/wslg/assets/2387408/c227acdc-426f-49a6-9d96-26486d6a8275

hideyukn88 commented 1 year ago

@castorfou, thanks for reporting the issue. While your case could be same issue as https://github.com/microsoft/wslg/issues/1092, but you seem to get a dump file at /mnt/wslg/dumps. If possible, would you please share that with us? thanks!

castorfou commented 1 year ago

Sorry I didn't see #1092. Do you want that I close this one? No dump is created when this problem happens. I have dumps in this folder though.

dumps.tar.gz

alonbl commented 10 months ago

Reproduced reliably using, this makes wsl unusable.

WSL version: 2.0.9.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.2428
jfdtse commented 10 months ago

Same issue here:

Versión de WSL: 2.0.11.0
Versión de kernel: 5.15.133.1-1
Versión de WSLg: 1.0.59
Versión de MSRDC: 1.2.4677
Versión de Direct3D: 1.611.1-81528511
Versión DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Versión de Windows: 10.0.22621.2428

/mnt/wslg/stderr.log reports:

[18:19:40.722] <5>WSLGd: Run:108: pid 441 exited with status 0, /init /mnt/c/Program Files/WSL/msrdc.exe msrdc.exe /v:70CE0337-B1D3-4468-B512-45BA2179C1D6 /hvsocketserviceid:F4C799B9-FACB-11E6-BD58-64006A7986D3 /silent /wslg /plugin:WSLDVC_PACKAGE /wslgsharedmemorypath:WSL\70CE0337-B1D3-4468-B512-45BA2179C1D6\wslg C:\Program Files\WSL\wslg.rdp
Error: debug scope named 'rdp-audio' is already registered.
Error: debug scope named 'rdp-audio-in' is already registered.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 569, clipping.
>                   X11 cannot support keycodes above 255.
> Internal error:   Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server

logs.tar.gz

alonbl commented 9 months ago

Dear @Microsoft Representative, Please review and merge #1108, #1092, #1098 bugs. Please acknowledge you accept the issue and working on a solution. Please tell us if you require any missing information from us users to make a progress. WSL is unusable when every network change/sleep/hibernate all applications need to be reopened. Forgive me that I am pasting this to all bugs, I do not know which if any you monitor. Thanks,

ryanjob42 commented 7 months ago

I'm running into this issue as well. Per another comment on #1098, opening any other GUI window causes everything to re-appear.

WSL version: 2.0.15.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.4116
tcostermans commented 6 months ago

I'm running into this issue as well. See: https://github.com/microsoft/wslg/discussions/1209


Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.4123```
shukryzablah commented 4 months ago

+1

Invarianz commented 3 months ago

Same issue when changing network interfaces or disabling them.

WSL version: 2.1.5.0
Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19044.4291