-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Comments
Since that command is only a mitigation, shouldn't this issue remain open until the root cause is fixed? |
I apologize, it appears a fix has already been committed 1ca0d82 |
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. |
Duplicate #3536 There are some workarounds you'll find useful in that thread. |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
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.
The text was updated successfully, but these errors were encountered: