-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_electrdNG9pL/chrome-sandbox is owned by root and has mode 4755. #6095
Comments
@tswaehn For previous instructions how to solve this, see #5371 (comment) Based on that I use jitsi/jitsi-meet-electron@4cc851d |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I'm still experiencing this targeting Linux arm64. |
@csett86 I am using the updated versions as below -- works like charm :) using the electron-quick-start example -- https://github.com/electron/electron-quick-start my package.json (modified for building dist)
building the dist
and finally running
works perfectly |
If your debian is now on debian 11, then yes, its now working without any issue out of the box, as debian 11 changed the default for kernel.unprivileged_userns_clone to 1. I suggest that you can then close this issue as its working fine (as you wrote) |
yes, will do. |
I am running default
electron-quick-start
app and just modified the package.json like below:then running
yarn run dist
works like charm.I am on
however when I attempt to run the appimage:
There are several "workarounds" like these
however this doesnt look like very "professional" - so I am wondering - what am I doing wrong?
The text was updated successfully, but these errors were encountered: