Skip to content
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

Closed
servomekanism opened this issue May 9, 2019 · 10 comments
Closed

Chrome-sandbox error can't start #167

servomekanism opened this issue May 9, 2019 · 10 comments
Labels

Comments

@servomekanism
Copy link

The appImage binary (./superProductivity-2.6.1-x86_64.AppImage) can't start on my linux box.
It reports the following:

zenity, kdialog, Xdialog missing. Skipping /tmp/.mount_superPjindcV/AppRun.
[5875:0510/021957.574089: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 /tmp/.mount_superPjindcV/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)
@ArjenR
Copy link

ArjenR commented May 10, 2019

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 sysctl in your kernel for this to be allowed.
kernel.unprivileged_userns_clone=1

@danielestevez
Copy link

It seems that workaround by @ArjenR or the solutions here electron/electron#17972 do not work with snap installed app -> scratux/scratux#1 (comment)
Still trying to find a solution,,,,

@ArjenR
Copy link

ArjenR commented May 10, 2019

I use the appimage. So if you cannot be without, perhaps downgrade to an ealier version or switch to appimage as workaround?

@danielestevez
Copy link

Never used appImage.
i won't downgrade just in case i get some data corruption 😨 and for AppImage i guess it's the same problem, i cannot export my data and import to the AppImage version

@ArjenR
Copy link

ArjenR commented May 10, 2019

The data is not stored inside the snap or appimage, but in your userprofile.
~/config/superProductivity/
Just make a backup of that one to be sure there is no corruption.

@danielestevez
Copy link

danielestevez commented May 10, 2019

btw i could open the snap version by running from the directory

/snap/superproductivity/current/superproductivity --no-sandbox

Now working in trying to recover my data

@johannesjo
Copy link
Owner

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.

@servomekanism
Copy link
Author

version 2.6.3 works in my system! ;)

@thomasnordquist
Copy link

The initial comment provides a workaround to disable the sandbox for Linux builds.
electron-userland/electron-builder#3872

@danielestevez
Copy link

danielestevez commented May 13, 2019

Thanks @johannesjo !! I can confirm the snap version works in Ubuntu without the workaround of kernel.unprivileged_userns_clone
EDIT: Guess we could close this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants