Joplin won't open on openSUSE Tumbleweed

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.

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

I have the same issue and I thought it was only me. I’m using the flathub version. It just sits in the background. Latest openSUSE Tumbleweed Wayland KDE version.

Not even the AppImage version opens even with APPIMAGELAUNCHER to FALSE.

I’m currently running the Windows version under wine, but it’s SLOW – even the typing is heavily delayed. It’s better than not having access to my notes though. The Linux version (AppImage or flatpak) will open under a X11 session of KDE, but I have other problems with x11 sessions, so that’s not an option for me.

I also have the same issue, Joplin 3.3.12 from Flathub, Fedora 43 with KDE Plasma 6.5.2. Joplin apparently runs and does stuff in the background but can’t open a window. Sometimes, randomly (~10% of the time), it works.

What fixed it for me was switching the flatpak permissions to Wayland : in KDE system settings > Application Permissions > Joplin > Manage Flatpak Settings > Advanced Permissions, uncheck X11 Windowing System and check Wayland Windowing System

I might also mention that I was using X11, but just now switched to Plasma Wayland just to see if it works and it does. So I’m using the AppImage-Version of Joplin 3.4.12, Tumbleweed 20251114, KDE 6.5.2 and Kernel 6.17-7. I have an old GP106 Nvidia Grafikkarte mit Nouveau-Treiber. So I’m afraid I don’t have a clue as to why so many folks are having problems with it. (Sorry I didn’t answer earlier, was not in house.)