search

microsoft / wslg

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

GUI locked up if application is running and Windows goes to sleep #1268

Open pappde opened 4 months ago

pappde commented 4 months ago

Windows Version

Microsoft Windows [Version 10.0.19045.4529]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

Kernel Version

5.15.153.1-microsoft-standard-WSL2

Distro Version

Ubuntu 22.04

Other Software

SmartGit 23.1.3

Repro Steps

  1. install SmartGit
  2. run SmartGit (using the start menu)
  3. observe UI responds correctly
  4. put Windows to sleep
  5. wake up Windows
  6. observe you can activate the SmartGit window, but cannot interact with it in any way. Appears frozen
  7. try to close through the taskbar, or by clicking "X"
  8. observe that doesn't work

Expected Behavior

Application should continue working and not be frozen.

Actual Behavior

Application is frozen. You can activate the window via the task bar, but it will not respond to any clicks. You cannot kill it from the task manager. You can kill it with "kill -9"

Diagnostic Logs

No response

github-actions[bot] commented 4 months 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 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](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.

pappde commented 4 months ago

NOTES:

  1. I reported this to SmartGit and they stated it may be a WSL bug, since they reproduced it with Windows 11 and Ubuntu 22.04 running another application "gedit".
  2. It is 100% repro
  3. I see the following spam error repeated in the application output: (SmartGit:488357): Gtk-CRITICAL **: 12:21:03.935: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar
pappde commented 4 months ago

WslLogs-2024-07-03_12-16-50.zip

github-actions[bot] commented 4 months ago
Diagnostic information ``` .wslconfig found Detected appx version: 2.2.4.0 ```
zc1036 commented 4 months ago

I observe the same issue. This happens when I run emacs built with Wayland. The app is "running" but it doesn't process user input, neither mouse nor keyboard presses. For example, I can resize it with the Windows+Arrow keys, but typing or clicking anywhere in the window is ignored. If I right-click on the taskbar button and click "Close window," the "Are you sure you want to exit emacs?" dialog will pop up within emacs, but I cannot interact with that dialog in any way.

Subsequently-created WSLG windows are perfectly functional though.

rowleya commented 2 months ago

This happens to me too, with chrome in Wayland mode. Works fine until I sleep / hibernate then when it wakes up the window is frozen. I can kill with "pkill chrome" from a WSL command line and then open it again.

As others have said, the application is not frozen, just the Window, as I can see things happening such as tabs opening from outside. Note that using "X11" mode appears to not freeze; I have eclipse in this mode and can use Chrome in that mode too without issue (but Chrome is ugly in that mode ;).

didibus commented 3 weeks ago

Same issue for me, Emacs in wayland. Very annoying, thinking my next laptop might be a mac because of this.

luigidcsoares commented 2 weeks ago

I'm also facing the same issue with Emacs.

terlar commented 2 weeks ago

I believe this issue might be the longstanding GTK issues in Emacs. I switched to lucid and haven't experienced this issue since. Which was quite frequent, prominent and disrupting to my daily workflow.