[Linux] AppImage not started, error about sandbox

[hever]

Hi, my desktop app stops working. When I run it from terminal I see this error message.

$ bin/standard-notes-3.0.16-x86_64.AppImage 
[9748:0913/101023.503973: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_standaT0U73Q/chrome-sandbox is owned by root and has mode 4755.

There are speaking about it - electron/electron#17972. So i try run with --no-sandbox and then it starts.

Debian GNU/Linux 9.11 (stretch)

[andrewferguson]

I don't know if this is a coincidence, but my Standard Notes appimage also stopped working yesterday, with the exact same error (only difference being the temporary file is .mount_standaJAs5Ys).

Thanks to the post above I was able to get it to run with --no-sandbox.

Also on Debian GNU/Linux, but version 9.9.

[javanophill902]

same problem here, started at the same time. debian stretch.
i still cannot open the app.

this is a bug
pls fix!

ps:
what is this --no-sandbox? what to write in command line? im newb to linux
pss : is running with --no-sandbox a security issue?

[hever]

what is this --no-sandbox? what to write in command line? im newb to linux

You can start app with command like this

$ /your/path/standard-notes-3.0.16-x86_64.AppImage --no-sandbox

[moughxyz]

Related forum thread: standardnotes/forum#690

[adds68]

Takes this as a time to point out that #172 is even more relevant than ever.

[pfctdayelise]

I don't have the app installed yet. When I tried to run it the first time, it tries to open with 'Software Install'. Is AppImage like a portable app or is it actually the installer?

[moughxyz]

AppImage is a portable app.

[er0k]

Same error on Debian sid:

$ uname -srv
Linux 5.3.0-2-amd64 #1 SMP Debian 5.3.9-3 (2019-11-19)

$ /opt/Standard-Notes-3.0.23.AppImage 
[12338:1127/165633.144100: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_StandaL2IOMb/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap

starting with --no-sandbox does work, but electron discourages this and says it should only be used for testing

[rendhalver]

It's only portable if it works everywhere without fail.

[arielsvg]

Here's an overview of this issue from the Electron team: electron/electron#17972 (comment)
I'm not quite sure there is something we can do here? 🤔 But I'm keeping this issue open right now just in case, wouldn't be a bad idea to check a newly packaged build at some point!

[chaserene]

happy to report that as of 3.8.21, this is no longer an issue for me. the appimage runs without --no-sandbox on Debian 11.

[JaspalSuri]

Thank you for taking the time to let us know, @chaserene! That's great to hear!

[gplcoder]

Long standing issue with many AppImage/Electron apps. Still does not run without the 'no-sandbox' option on MX Linux 19.x.

[JaspalSuri]

Sorry to hear that, @gplcoder. Thank you for taking the time to try that and for letting us know.