WSL/WSLg interoperability sometimes doesn't run correctly

[dcharlespyle]

On some sign-ons, WSL throws an error: "/bin/bash: /usr/bin/start-wsl-services: No such file of directory."

This, of course, involves a script I placed in WSL to run a few services on startup. Normally, this script runs just fine and starts services such as CUPS (so that I can print from Linux apps when desired), DBus system instance (so I can use the Trash in nautilus as well as some other apps that don't run correctly without a running system DBus session), and so forth. I understand that issues with my own script are not something for Microsoft to deal with (generally, until the last few updates, the script ran flawlessly) but the underlying issue is with interoperability of WSL and WSLg. When this error is generated, any BASH prompt opened while it is happening displays wslg [ ~ ]$ and no WSL GUI program will run. Some command line programs also won't run, either.

Sudo password is not accepted as per usual. Every single one of the programs showing in the above BASH session is installed in WSL, and properly configured. Sometimes, the problem will resolve itself. Sometimes it won't. Whenever this happens and it doesn't resolve itself, if I restart the LxssManager service WSL will terminate and then this problem vanishes, and WSL GUI programs will launch again, as well as other command line programs and scripts.

The following is what is expected to be seen when WSL and WSLg are running properly together on startup.

But when the BASH prompt is showing WSLg in the prompt, that is when the issues start. And they don't just involve my script used to launch Linux services.