No more launching appImage applications at startup after update 24.04

Herve · 2024-06-17T19:01:11.087Z

Operating system

Linux

Joplin version

3.0.8

Desktop version info

Version de Synchro : 3
Version du profil : 47
Trousseau supporté : Non

Révision : 826006c

Backup: 1.4.1
Favorites: 1.3.2
Note list (Preview): 1.0.0

What issue do you have?

Hello
1/ Since the update, I no longer have the launch of certain applications (Joplin, Ferduim) for which I put the command in "Applications at startup"

~$ sh -c 'sleep 2 && "/media/rv/data/Comp.com./Appli-data-port/Joplin/Joplin.AppImage"'
Setting $HOME to /media/rv/data/Com. computer/Appli-data-port/Joplin/Joplin.AppImage.home
[14056:0528/085134.690028: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_JoplinTlXjEW/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)

2/ Is the directory naming correct?

personalizedrefriger · 2024-06-17T19:09:50.620Z

I'm linking to a related GitHub issue:

github.com/laurent22/joplin

Joplin does not work in Ubuntu 24.04 due to apparmor issue

opened 01:44AM - 19 Apr 24 UTC

closed 12:52PM - 20 Apr 24 UTC

archisman-panigrahi

bug linux high

### Operating system Linux ### Joplin version 2.11.11 ### Desktop version in…fo _No response_ ### Current behaviour The Joplin appimage does not run in Ubuntu 24.04 due to recent changes in apparmor, which prevents all electron apps from running. For details, see https://github.com/electron/electron/issues/41066 and https://bugs.launchpad.net/apparmor/+bug/2046844 A temporary fix is described here https://github.com/electron/electron/issues/41066#issuecomment-1913509942 There is probably nothing the Joplin developers can do until apparmor fixes it, but I still wanted to report the bug to prevent huge confusion when 24.04 is released and thousands of users start using Joplin on it. ### Expected behaviour _No response_ ### Logs ``` $ ./Joplin.AppImage [9034:0418/214224.008705: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_Joplin8u3ir2/chrome-sandbox is owned by root and has mode 4755. ```

Herve · 2024-06-17T19:23:37.221Z

1/ Thank you for the quick reply. If I understand correctly there will be no quick resolution unless you put --no-sandbox (only solution for a non-developer but which would not be very secure?)

2/ Is the directory/file naming correct?

Herve · 2024-06-24T15:37:57.929Z

Hi
I see the previous message again. I'm using the new version 3.0.8, does this change anything?

Another suggestion: to have an option to launch Joplin automatically at startup!

Should I post this on github?

james-carroll · 2024-06-24T17:47:33.481Z

There's no (likely) scenario the requirement is dropped without either a native package installation or passing --no-sandbox, which the installation script should set up automatically.

The current official installation process is entirely unprivileged and can neither turn the security restrictions off nor grant itself an exception to them.

Herve:

2/ Is the directory/file naming correct?

There's no required structure so yes. Your structure is effectively just the default but with the AppImage native functionality to rewrite $HOME implicitly.

Herve:

Another suggestion: to have an option to launch Joplin automatically at startup!

It'd be nice if the app did this itself but as a workaround you should be able to add Joplin by path to the DE's startup list. This one again isn't actually too hard to get going but has complexities with the installation being an AppImage (I.E it's expected that integration is handled by the script, but not everyone will install with the script; some people will make their own autostart files, etc.)

Herve · 2024-06-24T18:04:43.314Z

ok thanks I'll wait. in the meantime I'll launch it manually

james-carroll · 2024-06-24T20:17:16.857Z

If you were happy to disable the security settings entirely, you could run

sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

This would let the AppImage work via double clicking and allow Electron to use its usual sandbox. If you've a lot of electron appimages it could be worth considering.

Herve · 2024-06-25T16:04:10.112Z

Hello
Thanks but I don't prefer to bypass security.
Eventually even if it's not very good, I understood that I could use ./Joplin.AppImage --no-sandbox while waiting for this problem to be taken into account

Herve · 2024-07-02T09:01:40.071Z

HI
For information, I can launch it in the terminal with the command
./Joplin.AppImage --no-sandbox
but not with
sh -c "/media/rvnux/donnees/Com.\ informat./Appli-donnees-port/Joplin/Joplin.AppImage --no-sandbox"

Herve · 2024-07-10T06:33:26.709Z

Hi
it works with
bash -c 'sleep 3 && /media/rv/donnees/Com.\ informat./Appli-donnees-port/Joplin/Joplin.AppImage --no-sandbox'

system · 2024-08-09T06:34:16.443Z

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.