It doesn't launch with AMD graphics

[3v1n0]

I'm getting this when launching it in AMD powered machine and no window is shown:

❯ joplin-desktop       
Error org.freedesktop.DBus.Error.Failed: cannot set "default-url-scheme-handler" subproperty "joplin" setting to invalid value "@joplin/app-desktop.desktop"
Sentry: Initialized with autoUploadCrashDumps: false
Gtk-Message: 17:28:27.443: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
/usr/share/libdrm/amdgpu.ids: No such file or directory
/usr/share/libdrm/amdgpu.ids: No such file or directory
[4075591:1016/172828.873791:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!

The initial ids error doesn't seem to be fatal though since the gpu-2404 driver seems to be picked...

[JGCarroll]

From a bit of Googling, this seems to be a common problem with Electron outside of Snaps, interestingly one user even mentions Joplin over a year ago: https://github.com/electron/electron/issues/32760

It's a shame this is happening with the gpu-2404 content snap, although could you please ensure that it's been used? Core24 was used for a week or so for the 3.0 releases currently on stable but was then reverted, although the 3.1 version in candidate still has it, so it's possible you have it installed from Joplin but it isn't actually being used at the moment.

It'd also be worth knowing whether Wayland is being used, and if so, whether running

joplin-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland

Makes a difference, or similarly, whether it runs better in a pure X11 environment.

Unfortunately though this looks like it's a nasty interplay between chromium and graphic drivers and it'd be worth seeing if there's other snaps in the same position as I imagine a proper fix is either in Chromium or Mesa itself.