Joplin under debian 10

Hello dear confinés !
To install joplin on my new desktop debian 10 computer, i used the given script as to install the AppImage.
I got this version : 1.0.197
I get this :

petit@debian:~/.joplin$ ./Joplin.AppImage
[21833:0418/] 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_JoplinqyTgY6/chrome-sandbox is owned by root and has mode 4755.
Trappe pour point d’arrêt et de trace

What should I do ?
Thanks !

First of all, Joplin is currently in the 200s on versions now. Secondly, if you run Joplin with —no-sandbox, you should be good to go. There was a massive amount of users on Debian running into this issue due to a kernel security flag. A quick search here and in the GitHub Issue Tracker, you’ll find out more about what all this about.

Hi bedwardly-down !
First of all, please note that I did not chose the version of jospin to be installed ; the script : `

wget -O - | bash`
did it for me ; it is perhaps time to upgrade this script ?
How do I do to get un newer version ?

it works well with --no-sandbox :heart_eyes:

Please, ggive me the links for GitHub Issue Tracker.

Thanks !

1 Like

Did you use the official means for getting Joplin or whatever Debian uses? The script should be up to date.

I used the script shown on main page :

Should probably be updated, amho.

Bises à la française !

1 Like

I’m trying to find it, but the issue may not be the script but how different Desktop Environments cache applications. The script is supposed to install the latest release but various DEs aren’t exactly respecting it and keeping older versions as their version of the app, if that makes sense.

If that’s the case, it’s not a bug but instead a design choice.

Desktop environments don’t actually change how an app behaves. It only changes the border and desktop

1 Like

They don’t but their Application Managers can. I’m trying to link the post but having some issues finding it. I read it yesterday and somebody had a similar problem either here or on the GitHub and discovered that the AppImage was downloading like it should but their DE AppManager wasn’t updating its entries for it.

EDIT: AppImage Launcher. Found the post: Desktop app version issue?

1 Like

I get your point. The app launcher behaviour does behave differently for different DE’s.

What is your Desktop Environment/Manager?

Gnome classic 3.30

I am not sure to understand correctly what you mean, but it could be usefull to inform you that it was my first install of joplin on my new computer. No old release there.
when installed and running, joplin informed me that a new release was existing an downloadable. So, I got the new release. Not yet installed (I don’t have any time for that just now).
Bises à la française.

See @RedDocMD‘s comment about that. I worded my comment wrong, but knowing as much info as possible is extremely useful. Thanks. :wink:

If you’re still having problems, there might be a bug with the script. We’ll need to see if others have the same issue and go from there.

Depending on how much you trust not being hacked while in your linux session…

# on Debian10, joplin sandbox will complain if we do not do this
sudo sysctl kernel.unprivileged_userns_clone=1

I never trust such things ; they are so hideous, monstrous, horrible.

Never trust what?

Never trust what?
Please, feel free to expect whatever could be pleasant to you.