I tried with 2.6.4 then 2.8.8 and finally 2.9.1. Sadly joplin deskt has been stuck for me and a specific computer. (Works on ubuntu 22.04 w/ Joplin 2.8.8.)
I get
~ $ ~/.joplin/Joplin.AppImage
xdg-settings: invalid application name
Try 'xdg-settings --help' for more information.
[6053:0716/152525.760526:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
and then nothing
hey, let's try renaming the profile folder (.config/joplin-desktop) and see if it makes a difference. Joplin should start empty.
Then it is a matter to figure out what exactly causing the problem: plugins or some of the data/settings.
You mention it works for you on Ubuntu 22.04 but what OS is it not working on?
Debian 10 buster
Kernel 5.10.0-0.bpo.15-amd64
Doing that, I saw that I had several joplin folders :
~/.config $ ls -lot | grep -i joplin
drwxr-xr-x 7 mehdi.guiraud 4096 juil. 16 23:56 joplin-desktop
drwx------ 11 mehdi.guiraud 4096 juil. 16 15:25 Joplin
drwxr-xr-x 4 mehdi.guiraud 4096 nov. 22 2021 joplin
drwx------ 3 mehdi.guiraud 4096 juin 1 2021 @joplin
This is the tail of the log (but I don't remember having encrypted any folder... )
2022-07-17 11:18:41: Synchronizer: "Sync: finished: Synchronisation finished [1658049520506]"
2022-07-17 11:18:41: Synchronizer: "Operations completed: "
2022-07-17 11:18:41: Synchronizer: "fetchingTotal: -"
2022-07-17 11:18:41: Synchronizer: "Total folders: 132"
2022-07-17 11:18:41: Synchronizer: "Total notes: 855"
2022-07-17 11:18:41: Synchronizer: "Total resources: 134"
2022-07-17 11:18:42: "DecryptionWorker: cannot start because no master key is currently loaded."
I removed all the non joplin-desktop file.
The folder joplin-desktop contains several folder and files. should'nt I delete only the cache folder ? :
~/.config/joplin-desktop $ du -s *
4164 cache
7384 database.sqlite
1852 kanban-logs.txt
4 log-autoupdater.txt
8 log-clipper.txt
2776 log-database.txt
192720 log.txt
3952 plugins
117280 resources
4 settings.json
4 templates
804 tmp
All of the folders you listed are relevant and needed for normal operation of joplin but joplin-desktop contains your data/settings.
if you don't have a fresh backup, please don't delete it just yet, just rename joplin-desktop and try to launch the application.
Once it runs successfully, notice folder plugins inside joplin-desktop. In most cases, one of the plugins may be responsible for the application crash/unresponsiveness. With some trial and error, you might be able to see what is causing a crash.
P.S. For now, let's not touch cache
I think older versions of Debian (like 10) need to have --no-sandbox appended to the command to launch the appimage.
This morning, Joplin-desktop started without issues.
Don't really what happenned. Any way thank you for you answers.
Thank you.
Hello Daeraxa,
I'm on Buster (Debian 10 with kernel 5.10.0-0.bpo.15-amd64).
didn't had to start with --no-sandbox, tho. It works well, now.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.