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

[Bug]: debian package : the app fails to start due to a permission issue #1561

Closed
wsourdeau opened this issue Jan 24, 2025 · 2 comments
Closed
Assignees
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@wsourdeau
Copy link

wsourdeau commented Jan 24, 2025

Can you reproduce this bug in the PWA?

No

Describe the bug

/opt/teams-for-linux/chrome-sandbox is not setuid root (user) after installation

What package are you using?

deb

Version

1.12.6

Reproduction steps

1. install the debian package
2. start Teams

Expected Behavior

The /opt/teams-for-linux/chrome-sandbox would be both owned by root and have mode 4755.
Suggestion : the postinst script could execute "chmod 4755 /opt/teams-for-linux/chrome-sandbox".

Debug

Running teams shows the following message :

"[8062:0124/175501.605834: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.
"

Additional context

No response

@wsourdeau wsourdeau added the bug Something isn't working label Jan 24, 2025
@nbuechner
Copy link

I also got that error on a fresh Ubuntu 24.04 installation. Setting owner and modes as suggested by the error message made it work.

@IsmaelMartinez
Copy link
Owner

IsmaelMartinez commented Jan 26, 2025

Thanks for reporting. This one is the same as #1426. Check the comments for a more permanent solution. You need to create an app armour profile.

This is a change by Ubuntu that electron and electron build have passed to the users. Hopefully they will find a nicer way to fix this.

@IsmaelMartinez IsmaelMartinez closed this as not planned Won't fix, can't repro, duplicate, stale Jan 26, 2025
@IsmaelMartinez IsmaelMartinez added the duplicate This issue or pull request already exists label Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants