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

Chromium Sandbox Permission Error Prevents SolidTime Launch #11

Open
mehmetkocer opened this issue Dec 26, 2024 · 3 comments
Open

Chromium Sandbox Permission Error Prevents SolidTime Launch #11

mehmetkocer opened this issue Dec 26, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@mehmetkocer
Copy link

Environment:

Operating System: Ubuntu 24.04 (amd64)
Desktop Environment: GNOME 46
Windowing System: X11

Description:
SolidTime application fails to launch due to incorrect sandbox permissions. The error occurs because the chrome-sandbox binary located at /opt/solidtime/chrome-sandbox lacks the required SUID permissions and ownership settings.
Error message:
image
text:
[19071:1226/122928.718752:FATAL:setuid_sandbox_host.cc(158)] 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/solidtime/chrome-sandbox is owned by root and has mode 4755.

Steps to reproduce:

Install SolidTime application from deb file
Attempt to launch SolidTime
Application immediately crashes with the above error

Expected behavior:

SolidTime should launch successfully with proper sandbox security enabled

Current behavior:

Application crashes immediately due to sandbox configuration error
Chrome-sandbox binary has incorrect permissions/ownership

@Onatcer Onatcer added the bug Something isn't working label Jan 1, 2025
@Onatcer
Copy link
Contributor

Onatcer commented Jan 1, 2025

Thanks for reporting, so I did not try to reproduce it yet but this is an issue with new Ubuntu 24.04 restrictions and it affects basically all Electron apps.

electron/electron#41066
electron/electron#42510

Electron Builder added support for AppArmor Profiles recently, which to my understanding should fix this issue, so we'll upgrade to this in the next version, hopefully, this resolves the issue. electron-userland/electron-builder#8635

But Electron-Builder v26 is currently still in Alpha, so I'd prefer to wait for a stable release. electron-userland/electron-builder#8636

There is a temporary workaround by disabling kernel.apparmor_restrict_unprivileged_userns, although I cannot comment on the exact security concerns so please use with caution.

sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

@mehmetkocer
Copy link
Author

Thanks for clarifying. I'll use the web app until this issue is resolved. I'm frustrated that Ubuntu frequently introduces unique breakages. Many users rely on numerous Electron apps, and it's annoying that Ubuntu seemingly disregards these issues, placing the burden on developers to constantly adapt to Ubuntu's changes.

@davidsmorais
Copy link

Can be easily fixed by running sudo chmod 4755 /opt/solidtime/chrome-sandbox

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants