Better experience for people not using .desktop file on linux

[ejade]

Bug Description

Every upgrade or fresh install of signal desktop on Debian gives the following error preventing it from starting:

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 /opt/Signal/chrome-sandbox is owned by root and has mode 4755

Workaround for this is: sudo chmod 4755 /opt/Signal/chrome-sandbox

Steps to Reproduce

install Latest debian stable. Install Signal-Desktop start signal desktop via terminal

Actual Result:

$ signal-desktop
[18010:0610/130805.625393: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 /opt/Signal/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap

Platform Info

Signal Version:

ALL versions of signal that i have tested or upgraded to is doing this

Operating System:

Debian 9 & 10

[scottnonnenberg-signal]

Please note that .desktop file included with the apt package shows how we recommend that the app is stated. We recommend the --no-sandbox command-line argument.

[zx2c4]

Why would you recommend people do that?

[prasket]

I was just trying out the beta and came across this issue.

@scottnonnenberg-signal I would also like to know why running without sandbox is recommended? Seems like that is the opposite of what should be done for a secure and private application, but maybe I am missing something so looking forward to learning. :)

[prasket]

@scottnonnenberg-signal never mind, I found this post from you in a PR from @zx2c4 :)

#4381 (comment)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.