code-insiders complains about mode and owner of chrome-sandbox being incorrect and refrains from starting. Happens with any recent insiders build.
Happes no matter what way of unpacking I come up with so the tarballs' internal may be broken.
Didn't happen ever before and disables any users that don't have root on their machine from using those builds.
$ ./code-insiders
[15113:0924/095256.312581:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly.
Rather than run without sandboxing I'm aborting now. You need to make sure that .../VSCode-linux-x64/chrome-sandbox is owned by root and has mode 4755.
[1] 15113 trace trap (core dumped) ./code-insiders
where ls -lasays
-rwxr-xr-x 1 mgritz Domain Users 5099032 Sep 12 02:54 chrome-sandbox
-rwxr-xr-x 1 mgritz Domain Users 112526104 Sep 12 02:54 code-insiders
Workaround (requires root): $ sudo chown root chrome-sandbox && sudo chmod 4755 chrome-sandbox
There's actually another workaround, which is our recommendation since it's virtually impossible for us to fix this while distributing tarballs: simply add --no-sandbox when invoking the electron executable directly. We do this automatically when you invoke the CLI script.
Workaround: use --no-sandbox.
