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 helper binary was found, but is not configured correctly. #1427

Closed
ondrej-simon opened this issue Sep 30, 2024 · 3 comments
Closed

Comments

@ondrej-simon
Copy link

Describe the bug

After updating to version 1.11.0, the following error appears, when trying to launch the application:

[25746:0930/073047.604531:FATAL:setuid_sandbox_host.cc(163)] 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/teams-for-linux/chrome-sandbox is owned by root and has mode 4755.

Seems to be caused by the Electron update and related to this issue: electron/electron#42510

To Reproduce

Steps to reproduce the behavior:

  1. Install Teams for Linux v1.11.0 on Ubuntu 24.04.
  2. Try to launch the application.
  3. Error.

Expected behavior

I launch the application and it launches.

Desktop:

  • OS: Ubuntu 24.04.1 LTS
  • Installation package: deb
  • Version: 1.11.0

Debug

Does not output anything extra besides the error mentioned at the beginning.

Additional context

Can be worked around by lifting Ubuntu's restrictions: electron/electron#42510 (comment), I am however pretty sure this is not the correct solution.

@IsmaelMartinez
Copy link
Owner

Thanks for reporting. I think is ok to do the 'no-sandbox' as modern Linux's now deal with sandboxing at a process level, but I need to read more about it before I just add it to everyones.

@piesarmin
Copy link

I've got this error last week.
I had to adapt the permissions of /opt/teams-for-linux/chrome-sandbox to 4755.
After the last update the error reoccurred.
So I had to adapt that again.
I don't understand why this issue is closed although it still exists.

@IsmaelMartinez
Copy link
Owner

@piesarmin , this issue is duplicated by #1426 . It is an ubuntu change that affects all electron apps. #1426 (comment) explains this in more details.

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

No branches or pull requests

3 participants