vscode: Using command line to open vscode causes code warning

Issue Type: Bug

Opening a folder in vscode using terminal causes this warning.

Warning: ‘sandbox’ is not in the list of known options, but still passed to Electron/Chromium.

VS Code version: Code 1.58.0 (2d23c42a936db1c7b3b06f918cde29561cc47cd6, 2021-07-08T06:53:55.113Z) OS version: Linux x64 5.8.0-59-generic snap Restricted Mode: No

System Info

Item	Value
CPUs	Intel® Core™ i5-8250U CPU @ 1.60GHz (8 x 2300)
GPU Status	2d_canvas: unavailable_software gpu_compositing: disabled_software multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: disabled_off rasterization: disabled_software skia_renderer: enabled_on video_decode: disabled_software vulkan: disabled_off webgl: unavailable_software webgl2: unavailable_software
Load (avg)	9, 6, 3
Memory (System)	7.66GB (0.37GB free)
Process Argv	–no-sandbox nodejsSelfStudy/ --crash-reporter-id 6f94af77-0e89-4dd0-91ba-5e3b74b9c614
Screen Reader	no
VM	0%
DESKTOP_SESSION	ubuntu
XDG_CURRENT_DESKTOP	Unity
XDG_SESSION_DESKTOP	ubuntu
XDG_SESSION_TYPE	x11

Extensions (48)

Extension	Author (truncated)	Version
project-manager	ale	12.2.0
wallpaper-setting	Ang	0.5.1
vscode-color	ans	0.4.5
docs-view	bie	0.0.9
npm-intellisense	chr	1.3.1
path-intellisense	chr	2.3.0
bracket-pair-colorizer	Coe	1.0.61
vscode-eslint	dba	2.1.23
es7-react-js-snippets	dsz	3.1.1
vscode-npm-script	eg2	0.3.22
prettier-vscode	esb	8.0.1
comment-anchors	Exo	1.9.5
vscode-open-in-application	fab	1.0.6
auto-close-tag	for	0.5.10
auto-rename-tag	for	0.1.6
code-runner	for	0.11.4
vscode-drawio	hed	1.5.0
search-node-modules	jas	1.3.0
node-module-intellisense	lei	1.5.0
python	ms-	2021.6.944021595
vscode-pylance	ms-	2021.7.2
jupyter	ms-	2021.8.1013163132
cpptools	ms-	1.5.0
sublime-keybindings	ms-	4.0.9
vscode-typescript-next	ms-	4.4.20210708
vsliveshare	ms-	1.0.4531
debugger-for-chrome	msj	4.12.12
vs-html-to-css	nep	1.0.0
material-icon-theme	PKi	4.8.0
material-product-icons	PKi	1.0.4
java	red	0.80.0
vscode-commons	red	0.0.6
vscode-xml	red	0.17.0
LiveServer	rit	5.6.1
vscode-fileutils	sle	3.4.5
pdf	tom	1.1.0
vscode-terminal-here	Tyr	0.2.4
vscodeintellicode	Vis	1.2.14
vscode-java-debug	vsc	0.34.0
vscode-java-dependency	vsc	0.18.5
vscode-java-pack	vsc	0.17.0
vscode-java-test	vsc	0.30.1
vscode-maven	vsc	0.31.0
nodejs-extension-pack	wad	0.1.9
JavaScriptSnippets	xab	1.8.0
markdown-all-in-one	yzh	3.4.0
material-theme	zhu	3.10.13
html-css-class-completion	Zig	1.20.0

(6 theme extensions excluded)

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt678:30270856
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551:30311712
vspre833:30321513
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255cf:30335482
vscorehov:30309549
vscod805:30301674
pythonvspyt200:30331937
vscextlangct:30333562
binariesv615:30325510
vstea450:30335276
bridge0708:30335490

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 51
Comments: 18 (2 by maintainers)

Commits related to this issue

fix: parsing of no-sandbox flag Fixes https://github.com/microsoft/vscode/issues/128279 — committed to microsoft/vscode by deepak1556 3 years ago
fix: parsing of no-sandbox flag (#128578) Fixes https://github.com/microsoft/vscode/issues/128279 — committed to microsoft/vscode by deepak1556 3 years ago

Most upvoted comments

On ubunut 20.04: I uninstalled my snap version, downloaded the .deb file, and installed it with apt

I did not loose my snippets or have to reinstall extensions!

The commands were

sudo snap remove code # saves snapshot for 31 days

# download .deb from web
sudo apt install ./code_<VERSION>_amd64.deb

vscode download

I also didnt see this before the June update so hopefully its fixed in the next one… but I want it gone now so Im happy with the reinstall

jfdoolster on Jul 13, 2021

Have the same problem on Ubuntu 20.04. Like others, used snap to install VS Code. I don’t think I ever saw this warning before the June update.

TheTrio on Jul 13, 2021

I am facing the same problem in elementary os, installed from snap

myvotop on Jul 14, 2021

I got the same issue… fedora 34 installed via snap

Version: 1.58.0
Commit: 2d23c42a936db1c7b3b06f918cde29561cc47cd6
Date: 2021-07-08T06:53:55.113Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Linux x64 5.12.14-300.fc34.x86_64 snap

kavin-du on Jul 13, 2021

same issue on ubutnu 21.04 installed via snap with sudo snap install --classic code

edit: launching a folder from terminal, with the verbose flag code <project> --verbose, I get this output

Warning: 'sandbox' is not in the list of known options, but still passed to Electron/Chromium.
[12643:0712/094658.008680:ERROR:node_bindings.cc(277)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
/snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so)
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
[main 2021-07-12T14:46:58.350Z] Sending env to running instance...
[main 2021-07-12T14:46:58.357Z] Sent env to running instance. Terminating...
[main 2021-07-12T14:46:58.357Z] Lifecycle#kill()

edit 2: I think it should be noted that I didn’t always get this error after a snap install. I was using vs code blissfully for a few weeks before this showed up. Is it maybe the result of a recent release?

therealphatmike on Jul 13, 2021

same issue here, ubuntu 20.04. vscode installed though snap with

sudo snap install --classic code

jfdoolster on Jul 12, 2021