-
-
Notifications
You must be signed in to change notification settings - Fork 955
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
Chrome-sandbox error can't start #167
Comments
Hi, I happened to run in to this one also. IIRC it is due to a new security option in Electron and user namespaces that needs to be enabled using |
It seems that workaround by @ArjenR or the solutions here electron/electron#17972 do not work with snap installed app -> scratux/scratux#1 (comment) |
I use the appimage. So if you cannot be without, perhaps downgrade to an ealier version or switch to appimage as workaround? |
Never used appImage. |
The data is not stored inside the snap or appimage, but in your userprofile. |
btw i could open the snap version by running from the directory
Now working in trying to recover my data |
Thanks everybody for looking into it. Don't have my linux laptop with me, but downgrading electron might fix this. Can't say if this will have any side effects though. I will publish a pre release in a minute or so (candiate/edge channel for the snap version). Would be really nice if someone could test this and report if the issue still persists. |
version 2.6.3 works in my system! ;) |
The initial comment provides a workaround to disable the sandbox for Linux builds. |
Thanks @johannesjo !! I can confirm the snap version works in Ubuntu without the workaround of |
The appImage binary (./superProductivity-2.6.1-x86_64.AppImage) can't start on my linux box.
It reports the following:
The text was updated successfully, but these errors were encountered: