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.

[Patrck-C]

• This is not a feature request (existing functionality does not work, not missing functionality).
  I will request features on forum or via support.
• I've searched and did not find a similar issue.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

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):

• OS: [e.g. iOS]
• Desktop Environment, if applicable (on Linux)
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[spastis]

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.
Trace/breakpoint trap (core dumped)

[charlag]

You might need to install fuse2

[spastis]

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

[castarco]

I'm having basically the same problem. Installing fuse2 does not fix it.

As a temporary workaround (found here: #1565 a bug still open since 2019), we can run tuta --no-sandbox... but there are plenty of reasons to dislike this hack.

[castarco]

@charlag

You might need to install fuse2

Ubuntu 24.04 installs fuse3, I guess they have their reasons.

When we manually install fuse2, fuse3 is automatically replaced by its older counterpart. I'm not sure this is a good thing. On the other hand, the problem is not solved by switching to fuse2.

[antonlydell]

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?

[pappasadrian]

Same issue here, after updating to Ubuntu 24.04 from 23.10.
The app will launch when double clicking on the appimage, but will not launch through desktop integration or through the terminal. Executing the app through the terminal throws the following error:

[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.
Trace/breakpoint trap (core dumped)

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

[charlag]

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

[charlag]

see AppImage/AppImageKit#877

[crazD802]

Same issue here on Ubuntu 24.04
The app will launch when double clicking on the appimage, but will not launch through desktop integration or through the terminal. Executing the app through the terminal throws the following error:

[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.
Trace/breakpoint trap (core dumped)

[Samueru-sama]

Looks like you are affected by this issue caused by apparmor changes in ubuntu.

linux mint reverted the change, and solus dropped apparmor all together. You might want to consider reporting the issue to kubuntu.

---

When we manually install fuse2, fuse3 is automatically replaced by its older counterpart. I'm not sure this is a good thing. On the other hand, the problem is not solved by switching to fuse2.

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

fuse2 and fuse3 were made to be installed together and can be done in archlinux for example (archlinux actually still uses fuses2 as the "main" fuse). But on debian based distros that's not possible.

With that said, there is a way to make a appimage that doesn't depend on libfuse2, and that is if you use this appimagetool which uses the statically linked runtime and the cemu emulator for example has been using for a long time already.

go-appimage also has a deploy everything mode which makes the appimage be able to work on any linux distribution, that is very old distros or even musl distros.