Displays do not go to sleep when WSLg is enabled after unlocking Windows lock screen using modifier key (such as left-ctrl)

[desultory-zz]

Environment

Windows build number:  Version 10.0.22000.100
Your Distribution version:  Gentoo 17.1 Hardened
Your WSLg version:  1.0.24

Steps to reproduce

Just have WSLg running

C:\WINDOWS\system32>powercfg /requests
DISPLAY:
[PROCESS] \Device\HarddiskVolume4\Windows\System32\mstsc.exe
RAIL Power Request

Expected behavior

Screen should go to sleep after 15 minutes

Actual behavior

Display never goes to sleep when WSL is running

[hideyukn88]

@desultory, thanks for reporting the issue. Do you run any Linux GUI application ? and if so, could that application be updating screen periodically? Please refer #172. thanks!

[desultory-zz]

This happens even if I just open WSL session with no GUI. I only installed tigerVNC to test wslg, nothing else.

[hideyukn88]

@desultory , would you please take a look /mnt/wslg/weston.log and see if you have any log with "rdp_rail_idle_handler is called" or "rdp_rail_wake_handler is called" ? thanks!

[desultory-zz]

@hideyukn88

1700 is when I booted, 0200 is when I had a VNC session

This is that file, grepped for "rail" with lines above and below

               https://wayland.freedesktop.org
               Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
               Build: 9.0.0-30-ged4f3bbb
[17:33:34.242] Command line: /usr/bin/weston --backend=rdp-backend.so --xwayland --shell=rdprail-shell.so --logger-scopes=log,rdp-backend,rdprail-shell --log=/mnt/wslg/weston.log
[17:33:34.242] OS: Linux, 5.10.43.3-microsoft-standard-WSL2, #1 SMP Wed Jun 16 23:47:55 UTC 2021, x86_64
[17:33:34.243] Using config file '/home/wslg/.config/weston.ini'
[17:33:34.244] Output repaint window is 7 ms maximum.
--
[17:33:34.256] RDP backend: Environment dump - end
[17:33:34.256] Using external fd for incoming connections: 3
[17:33:34.256] Default head is being added
[17:33:34.256] Registered plugin API 'weston_rdprail_api_v1' of size 56
[17:33:34.256] RDPAPPLIST_MODULEDIR is set to /usr/lib/rdpapplist
[17:33:34.258] RDP backend: use_rdpapplist = 1
[17:33:34.267] RDP backend: use_gfxredir = 1
--
               screen capture uses y-flip: no
               presentation clock: CLOCK_MONOTONIC_RAW, id 4
               presentation clock resolution: 0.000000001 s
[17:33:34.270] Loading module '/usr/lib/weston/rdprail-shell.so'
[17:33:34.271] RDPRAIL-shell: WESTON_RDPRAIL_SHELL_DEBUG_LEVEL: 3.
Date: 2021-07-29 CDT
[17:33:34.271] wet_shell_init: distro name Gentoo (6)
--
[17:33:34.274] WSL2_DEFAULT_APP_OVERLAY_ICON:/usr/share/icons/wsl/linux.png
[17:33:34.274] WESTON_RDPRAIL_SHELL_DISABLE_BLEND_OVERLAY_ICON_TASKBAR:1
[17:33:34.274] WESTON_RDPRAIL_SHELL_DISABLE_BLEND_OVERLAY_ICON_APPLIST:1
[17:33:34.274] rdp_rail_shell_initialize_notify: shell: distro name: Gentoo
[17:33:34.275] app_list_monitor_thread: running in system-distro with user-distro: Gentoo
[17:33:34.275] app_list_monitor_thread: open(/proc/self/ns/mnt)
[17:33:34.275] app_list_monitor_thread: open(/proc/2/ns/mnt)
--
[17:33:35.061] Translated workarea:(1920,0)-(3840,1032) at rdp-0:(1920,0)-(3840,1080)
[17:33:35.061] Client ExecOrder program terminated
[17:33:35.061] dummy-entry exited with status 255
[17:33:35.061] rdp_rail_notify_app_list(): rdp_peer 0x56148b049130
[17:33:35.061]     inSync: 1
[17:33:35.061]     syncStart: 1
[17:33:35.061]     syncEnd: 0
--
[17:33:35.061]     appDesc: FLUID (Gentoo)
[17:33:35.061]     appIcon: 0x7fb758002070
[17:33:35.061]     appProvider: (null)
[17:33:35.062] rdp_rail_notify_app_list(): rdp_peer 0x56148b049130
[17:33:35.062]     inSync: 1
[17:33:35.062]     syncStart: 0
[17:33:35.062]     syncEnd: 1
--
[17:33:35.141] Audio sink thread: Listening for audio connection.
[17:33:39.292] Audio sink thread: connection successful on socket (82).
[17:33:39.292] RDP Sink version (1 - 1)
[17:38:35.045] rdp_rail_idle_handler is called on peerCtx:0x56148b049130
[21:22:28.204] rdp_rail_wake_handler is called on peerCtx:0x56148b049130
[21:27:28.204] rdp_rail_idle_handler is called on peerCtx:0x56148b049130
Date: 2021-07-30 CDT
[00:22:19.154] Client: DisplayLayoutChange: monitor count:0x3
[00:22:19.154] Client: DisplayControl: monitor count:0x3
--
[02:03:30.967] xfixes selection notify event: owner 2097153
[02:03:30.967] our window, skipping
[02:03:50.556] Didn't find output containing (-31, -12), return default
[02:03:50.584] rdp_rail_wake_handler is called on peerCtx:0x56148b049130
[02:03:50.694] Client: ClientGetAppidReq: pid:156 appId:Vncviewer
[02:03:52.583] !!!cursor role is added after creation - WindowId:0x1
[02:04:10.947] Didn't find output containing (-31, -12), return default

[gordallott]

Also have this issue, powercfg -requests in an elevated powershell prompt gives

PS C:\WINDOWS\system32> powercfg -requests
DISPLAY:
[PROCESS] \Device\HarddiskVolume4\Windows\System32\mstsc.exe
RAIL Power Request

SYSTEM:
[PROCESS] \Device\HarddiskVolume4\Windows\System32\mstsc.exe
RAIL Power Request

AWAYMODE:
None.

EXECUTION:
None.

PERFBOOST:
None.

ACTIVELOCKSCREEN:
None.

zero wslg windows open

[desultory-zz]

Updating my kernel seemed to fix it temporarily, but I noticed that if I ever opened a WSLg window, it would not go to sleep normally until I rebooted the whole system. I have not used WSLg since then but at least it goes to sleep when running normally through the terminal.

[hideyukn88]

Hi @desultory, thanks for providing more info. Do you observe this issue with any WSLg app? for example, if you launch 'xclock', then close 'xclock' (so no more WSLg app is running on desktop), then display never turned off? Or is this only happens when ' tigerVNC' is ever used? thanks!

[gordallott]

to note, this happens with any wslg app, opening xclock and closing xclock keeps the display open, as my comment pointed out, mstsc.exe keeps the remote desktop connection going which keeps the system from sleeping

[ebroder]

I've started seeing similar behavior within the last week or so. (If it seems like this is a different bug, let me know and I'd be happy to file separately). My computer seems to not go to sleep if WSL is running at all, even if I've never started a WSLg app. If I run wsl --shutdown, then everything seems to get cleaned up. I dumped logs at https://gist.github.com/ebroder/7143b922985281cd817a535d938cab31 but can grab more if helpful.

[jclark]

I just installed Windows 11 and then WSLg, and also found that my computer no longer sleeps. Disabling WSLg by putting

[wsl2]
guiApplications=false

in .wslconfig got my computer sleeping again (but no WSLg of course).

[vladimir-novoseltsev]

For me just starting WSL is not enough to trigger this. I had to run some app which would use WSLg, then until WSL is explicitly shutdown displays would not turn off.

[desultory-zz]

Hi @desultory, thanks for providing more info. Do you observe this issue with any WSLg app? for example, if you launch 'xclock', then close 'xclock' (so no more WSLg app is running on desktop), then display never turned off? Or is this only happens when ' tigerVNC' is ever used? thanks!

most recently I noticed it keeping my computer awake when using firefox. I was using it with Selenium for what it's worth and when I closed that program it seemed to sleep properly.