Linux: Unable to launch Code after upgrade to 1.57

[erikfroseth]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version:
  1.57.0
  b4c1bd0
  x64

• OS Version:
  Ubuntu 20.04.2 LTS

Steps to Reproduce:

1. Upgrade vscode to latest version using apt
2. Start vscode either by clicking the icon in Gnome, or writing "code" in the terminal

I know this bug report doesn't help much, but I do not know what else to include. I did "apt update" this morning, and vscode stopped working after this. When writing "code" in my terminal, nothing happens. No output, nothing. The same has happened to a colleague with the same OS/machine. If there is anything more I should add (logs, etc), I would be more than happy to include it.

I noticed that there are some bug reports on the settings file being corrupted, but that does not seem to have happened to me.

[bpasero]

Does it work when you run code --no-sandbox?

[erikfroseth]

@bpasero Yes, that works!

[bpasero]

@erikfroseth how did you install VSCode? Snap?

[erikfroseth]

I installed it using this guide: https://code.visualstudio.com/docs/setup/linux#_debian-and-ubuntu-based-distributions

Downloaded the .deb and did the following steps:

sudo apt install apt-transport-https
sudo apt update
sudo apt install code # or code-insiders

[bpasero]

Any chance you are running code as sudo?

[erikfroseth]

No, I'm not running code as sudo. If I try running it as sudo, I get a warning saying You are trying to start Visual Studio Code as a super user ...

[bpasero]

How about running with --disable-setuid-sandbox?

[erikfroseth]

It still does not start. It gives me a warning, though: Warning: 'disable-setuid-sanbox' is not in the list of known options, but still passed to Electron/Chromium.

However, I see that entering "code" in my terminal does start some processes that never dies:

erikfroseth@erik-desktop:~$ ps -A | grep code
erikfroseth@erik-desktop:~$ code
erikfroseth@erik-desktop:~$ ps -A | grep code
  43167 ?        00:00:00 code
  43170 ?        00:00:00 code
  43171 ?        00:00:00 code

[Ekmansoft]

I have the same problem. It seems to have started after an update tonight. Running Debian 10

Linux pc35826-1930 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Lin

[deepak1556]

@erikfroseth can you make sure to kill all code processes and then try #126019 (comment)

[erikfroseth]

@deepak1556 Still the same problem :-(

[Ekmansoft]

@deepak1556 Still the same problem :-(

Me too

[Ekmansoft]

Killing the processes worked fine, and now no more processes appears, but still no sign of vscode starting

[bpasero]

We will push #126027 for May recovery which will restore --no-sandbox.

[erikfroseth]

@bpasero Big kudos to you and the team for super fast response! Thank you very much for your help