Joplin stopped to work on my Fedora KDE 43

Support
1

Operating system

Linux

Joplin version

3.4.12

Desktop version info

Can't open 'About' because the app doesn't even start. See below.

Sync target

File system

What issue do you have?

Joplin stopped working on my Fedora KDE 43. It doesn't even open. Getting this error message: bruno@fedora:~/AppImages$ ./Joplin-3.4.12.AppImage Sentry: Initialized with autoUploadCrashDumps: false [171226:1201/202539.865559:ERROR:mime_util_xdg.cc(137)] Invalid mime.cache file does not contain null prior to ALIAS_LIST_OFFSET=44 [171226:1201/202539.867214:ERROR:mime_util_xdg.cc(137)] Invalid mime.cache file does not contain null prior to ALIAS_LIST_OFFSET=44 [171264:1201/202612.258022:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [171264:1201/202612.264410:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!

2

Upgrading to the 3.5.x pre-release might help. See Joplin AppImage/Flatpak fail to start on Wayland + NVIDIA (GPU process crash). Only Snap version works. · Issue #13830 · laurent22/joplin · GitHub.

3

I run Joplin on Fedora 43, but with the GNOME desktop.

I install using an RPM. But the RPM houses the exact same AppImage, so I am not sure why you are experiencing this problem.

If you want to try it:
https://copr.fedorainfracloud.org/coprs/taw/joplin/

Question: Did 3.4.12 work at some point in time and now it is not working? Or did you upgrade the OS or Joplin and then it stopped working?

4

AI is telling me that your mime cache is corrupted somehow and to try this:
sudo update-mime-database /usr/share/mime

And I presume also do this:
update-mime-database ~/.local/share/mime

6

Thanks, done that but I’m still getting error messages (see my reply to @personalizedrefriger )

7

Thanks, I’m still getting errors (see below) but at least the prerelease opens and allows me to access my notes. Here are the error messages I’m still getting: ```Sentry: Initialized with autoUploadCrashDumps: false
[2704393:1203/222218.892851:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:273] Unable to set image transfer function.
[2704393:1203/222218.892868:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:191] Failed to populate image description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range
:FULL}
[2704393:1203/222220.095314:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:273] Unable to set image transfer function.
[2704393:1203/222220.095331:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:191] Failed to populate image description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range
:FULL}
[2704393:1203/222220.095339:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_management_surface.cc:63] Failed to get image description for color space.
[2704393:1203/222221.299210:ERROR:base/nix/mime_util_xdg.cc:139] Invalid mime.cache file does not contain null prior to ALIAS_LIST_OFFSET=44
[2704393:1203/222221.302403:ERROR:base/nix/mime_util_xdg.cc:139] Invalid mime.cache file does not contain null prior to ALIAS_LIST_OFFSET=44

8

‘Question: Did 3.4.12 work at some point in time and now it is not working? Or did you upgrade the OS or Joplin and then it stopped working?’ Both. I updated Fedora KDE from version 42 to 43 and after some time the stable version of Joplin refused to start. Used to run the flatpak version. Tried then to install from the official Fedora repositories via ``sudo dnf install`` and finally went with the official appimage, all to no avail. This far the only thing that worked was installing the prerelease version (I’m currently on 3.5.9).

1 Like