Operating system
Linux
Joplin version
3.3.12
Desktop version info
Can't open to the app to report that information.
What issue do you have?
It won't open at all. When I run it from the console, I get the following:
LaunchProcess: failed to execvp:
xdg-settings
Sentry: Initialized with autoUploadCrashDumps: false
The version I normally run is that from Flathub, but in this case I also tried the AppImage version which results in the same output. It's being run within a KDE Plasma 6.5 (wayland) session.
I tried removing all Joplin related directories in both ~/.local/ and ~/.config, and although the files were generated correctly when the app was executed, the outcome was the same, in addition to the console output.
I’ve tried the “isMaximized” tweak to window-state-prod.json, and that doesn’t seem to help.
Aid is appreciated. Thank you.
2 Likes
I’m running into the same issue and have been since I updated on Wednesday.
Same thing for me:
.joplin/Joplin.AppImage
Sentry: Initialized with autoUploadCrashDumps: false
This appears to be resolved after updating KDE Plasma to 6.5.1. I’m giving it a little time before calling it, but so far, Joplin is opening correctly again.
I take that back. It is working on one machine but not the other. I realized I had an old AppImage of Joplin version 3.0 so I tried running that – it opens correctly. Version 3.4 does not.
I had the same problem on my laptop starting today. I did discover, however, that I could start Joplin from the command line (the same command line as in the desktop icon). I’m using OpenSuse Tumbleweed 20251109 and KDE 6.5.2.
In the icon I set the environment variable APPIMAGELAUNCHER to FALSE. Then Joplin could also be started with a double click on the icon again!
Oddly enough, it does continues to work normally on my desktop. I do use a higher resolution monitor on the laptop, on which it won’t start anymore from the icon.
@werdenfelser what kind of Joplin install do you have? Flatpak? AppImage? I can’t get ether to run that way. Also, it’s now failing on both of my machines again. It’s very odd.
Oh yeah, I forgot to mention that – it’s AppImage.
I can’t replicate that – it’s still failing for me. I’m using a Wayland session, however. I wonder if that has something to do with it.