-
Notifications
You must be signed in to change notification settings - Fork 503
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
No longer works after upgrade to Kubuntu 24.04, it was fine with 23.10. Starting totanota-desktop-linux, nothing happens, no process is created. I've re-downloaded the program, but same thing. #6993
Comments
I have the same issue since the upgrade to Kubuntu 24.04. If I open it via the terminal I get the following error: [8471:0527/115418.173195: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 /tmp/.mount_tutanoA4hZw3/chrome-sandbox is owned by root and has mode 4755. |
You might need to install fuse2 |
Thank you for the reply. It is already installed. Like OP I did not have this issue before the upgrade from 23.10 to 24.04 |
I'm having basically the same problem. Installing As a temporary workaround (found here: #1565 a bug still open since 2019), we can run |
Ubuntu 24.04 installs When we manually install |
have the same issue aswell on Ubuntu 24.04. It seems similar to this issue in Bitwarden : Please stop packaging the Desktop client with a setuid root chrome-sandbox Is it a secure workaround? |
Same issue here, after updating to Ubuntu 24.04 from 23.10. [63086:0617/145944.011147: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 /tmp/.mount_tutanonlBDn7/chrome-sandbox is owned by root and has mode 4755. getting an appimage to work is already somewhat burdensome for novice users, imo. Fiddling with installed fuse2/3 versions and/or "--no-sandbox" flags in the executable is also too confusing and breaks UX entirely. Thus this issue needs addressing asap, in my opinion |
You do not need sandbox. This is very not ideal, we would like to have an easier way to install but afaik to fix AppImage they need to allow using new fuse and/or link statically |
Same issue here on Ubuntu 24.04 [138301:0618/233131.179499: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 /tmp/.mount_tutanogFna8J/chrome-sandbox is owned by root and has mode 4755. |
I will request features on forum or via support.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: