The VS Code app cannot be opened.

[go2run]

• After installation, it will immediately encounter an error, cannot be opened, and the app window will not appear.

• Host OS Version: Windows 11

• Host GPU Model and Driver/Encoder Version: NVIDIA RTX 3050Ti

• Browser Version: Edge 151.0.4129.93

• Docker in WSL

• I confirm that this issue is relevant to the scope of this project. If you know that upstream projects are the cause of this problem, please raise the issue there.

• I confirm that I have read other open and closed issues and that duplicates do not exist.

• I confirm that the issue is easily reproducible and explained thoroughly.

• I confirm that relevant log files have been included as explained below. Any relevant additional log files have also been included.

• I confirm that no portion of this issue contains credentials or other private information, and it is my own responsibility to protect my privacy.

• I confirm that the authors of this issue does not willfully breach or infringe legal regulations, in any and all global law, regarding trademarks, trade names, logos, patents, or any and all other forms of external intellectual property, as well as adhering to software license terms of open-source and proprietary software projects.

[ehfd]

I think the fix has something to do with --no-sandbox or similar (you tend to need this).

[ehfd]

What kind of errors?

[go2run]

I'm not sure what you mean by "flag".

Currently, when I click "Start", a new environment appears,

and then it just stays on this black screen.

Even if you press the start button

So dark...

All other functions are normal.

[go2run]

Wait, I opened it, but it opened like this, which isn't normal...

[ehfd]

@thelamer Anything you know about this?

[junkerderprovinz]

Two data points, because the --no-sandbox idea can be ruled out.

It is already there, and has been since the first commit: apps/vscode/entrypoint is code --no-sandbox "$@" (linuxserver/proot-apps@9fb6b41, April 2024). Confirmed on a running instance as well, the actual process is /usr/share/code/code --no-sandbox.

Second, it works on Linux. I installed vscode through proot-apps in a Debian XFCE container and launched ~/.local/bin/vscode-pa: the process tree comes up, the window title is "Welcome - Visual Studio Code", and stderr stays completely empty. So the app and the image look fine, which points at the WSL side.

@go2run for the error output you were asked about, open a terminal inside the desktop and run the launcher directly rather than clicking the icon:

~/.local/bin/vscode-pa

Whatever Electron complains about shows up there, which a screenshot cannot capture. If the window does appear but stays black, the next useful test is whether rendering is the problem:

~/.local/bin/vscode-pa --disable-gpu

If it draws normally with that flag, it is the GPU path, and on WSL that means the /dev/dxg and Mesa D3D12 side rather than anything in selkies.

[junkerderprovinz]

Follow-up on the --no-sandbox point above.

One thing that might be worth considering is a wrapper that applies the flag, rather than having it named in the Dockerfile. That is about chrome rather than VS Code, so it does not change what I wrote here, but it may be the tidier shape either way.

Happy to try a wrapper on my end if that would help.