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

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

Open
2 tasks
Patrck-C opened this issue May 23, 2024 · 12 comments
Labels
bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues

Comments

@Patrck-C
Copy link

Patrck-C commented May 23, 2024

  • 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.

@Patrck-C Patrck-C added bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues labels May 23, 2024
@spastis
Copy link

spastis commented May 27, 2024

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
Copy link
Contributor

charlag commented May 27, 2024

You might need to install fuse2

@spastis
Copy link

spastis commented May 27, 2024

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
Copy link

castarco commented Jun 5, 2024

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
Copy link

castarco commented Jun 6, 2024

@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
Copy link

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
Copy link

pappasadrian commented Jun 17, 2024

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
Copy link
Contributor

charlag commented Jun 17, 2024

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
Copy link
Contributor

charlag commented Jun 17, 2024

see AppImage/AppImageKit#877

@crazD802
Copy link

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
Copy link

Samueru-sama commented Jul 20, 2024

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.

@stecog
Copy link

stecog commented Sep 3, 2024

Thanks @Samueru-sama , I've solved with:

echo 'kernel.apparmor_restrict_unprivileged_userns = 0' | sudo tee /etc/sysctl.d/20-apparmor-mint.conf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues
Projects
None yet
Development

No branches or pull requests

9 participants