Community-edition: Rambox 7.0 appimage Linux 64 bit crashes on start with "SUID sandbox helper binary was found"

[laszlokertesz]

Steps to reproduce

1. Trying to start rambox from appimage
2. 
   
   
   3.
   

Expected behavior

It starts?

Actual behavior

It does not start.
In terminal it shows this error:

[4226:1120/115207.508608: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_rambox6n1T2d/chrome-sandbox is owned by root and has mode 4755.

I cannot do anthing since the mount specified there is not persistent. Other Electron apps (not appimage) had the same issue but they pointed towards an existing binary that i could chmod.

/tmp is mounted with these options:

tmpfs on /tmp type tmpfs (rw,nodev,noatime,size=3145728k)

ENVIRONMENT

Debian testing 64 bit

Rambox: v0.7.0

OS: XXXX

Arch: x64 or ia32
64

[welcome[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[freezed]

Same message for .deb package.

See this electron #17972 comment

[fvulich]

Did you try launching Rambox with --no-sandbox flag?

[freezed]

Yep, rambox --no-sandbox runs well :+1:

[Mef45]

Did you try launching Rambox with --no-sandbox flag?

Yep, rambox --no-sandbox runs well

That's not a good solution.

[freezed]

Ok, what could be a good solution?

[Mef45]

Ok, what could be a good solution?

run with --no-sandbox by default, or something else, idk

but not at all like 'hey, you're installed our app, now go to google and find how to run it correctly, lol, run it from terminal each time with custom params, or create new running scripts, but not just install and start to use, 'cos linux is for hardcore users only'

But that's only my opinion it this situation.

[freezed]

I see, my long answer had to be :

rambox --no-sandbox runs well Rambox, but I have no idea of the consequences of using this option.

[nordcomputer]

Same issue here with 0.7.1 on Debian Buster and the AppImage...
and I figured it out, because of the Auto-Update...

[mmlo]

temporary fix:
sudo chmod 4755 PATH-TO/chrome-sandbox

[fvulich]

It's an electron related issue, we are working to get a better fix, the --no-sandbox switch seems to be the fix less intrusive.

[cchris-org]

Same on deb Package. Would it probably better to deploy deb and appImage with --no-sandbox in startup cmd?

[Scibearspace]

Just downloaded the Rambox-0.7.5-linux-amd64.deb to my system.

This issue may be closed, but I ran into the exact same problem. I agree with @cchris-org that the app should be deployed with the --no-sandbox in the startup command. Escpecially as @fvulich suggested this is a < less intrusive > fix.