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

The SUID sandbox is not configured correctly. #3566

Closed
bunyaminaktas opened this issue Sep 6, 2019 · 4 comments
Closed

The SUID sandbox is not configured correctly. #3566

bunyaminaktas opened this issue Sep 6, 2019 · 4 comments

Comments

@bunyaminaktas
Copy link

bunyaminaktas commented Sep 6, 2019

Bug Description

Signal desktop application cannot be started and it gives the error that is below when trying to open it from terminal. This issue has occurred after the latest upgrade.

_[11373:0906/130348.561215: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.
_

Steps to Reproduce

  1. Write signal-desktop to the terminal.
  2. See the error output.

Actual Result:

The command prints an error output and doesn't open the app.

Expected Result:

The app should open normally.

Platform Info

Signal Version:

1.27.1

Operating System:

Debian 9.9

Edit:
I had tried chmod 4755 /opt/Signal/chrome-sandbox before opening the issue but it hadn't solved the problem. Now, I removed and reinstalled the package and used the command, then the problem has gone.

@rkoesters
Copy link

Since that command is only a mitigation, shouldn't this issue remain open until the root cause is fixed?

@rkoesters
Copy link

I apologize, it appears a fix has already been committed 1ca0d82

@bunyaminaktas
Copy link
Author

bunyaminaktas commented Sep 8, 2019

I have upgraded the app to ver. 1.27.2 now. It starts when I click its icon but when I try to start it via terminal it gives the same error.

@bunyaminaktas bunyaminaktas reopened this Sep 9, 2019
@scottnonnenberg-signal
Copy link
Contributor

Duplicate #3536

There are some workarounds you'll find useful in that thread.

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

No branches or pull requests

3 participants