-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The SUID sandbox helper binary was found, but is not configured correctly #1209
Comments
You can workaround this by running the AppImage with --no-sandbox option. If this has any security implications, however, I'd be interested to know. |
Doing some dig into Electron...it seems like this is a known issue of sorts. Not sure that 4755 will solve this (also as explained in PR comment, it just raises some new errors). It seems like --no-sandbox is being suggested as the workaround/hack to get this to work. In some places (like snap) this has even been embedded into the ./AppRun. To me this seems drastic -- first sentence in electron docs on sandbox: "One of the key security features of Chromium is that all blink rendering/JavaScript code is executed within a sandbox." https://www.electronjs.org/docs/api/sandbox-option I'm still learning Electron, so I'm not an expert here. But this seems like an issue worth addressing. |
I honestly don't know what else I can do to work around this issue. The way I changed it in the pull request is based on what they do here and while it gets rid of the original error message, it obviously just delays the problem. You could also try |
Failed to start app image for the first time as non-root user:
The text was updated successfully, but these errors were encountered: