Modrinth app won’t launch after updating

[twigtarsier]

Please confirm the following.

• [X] I checked the existing issues for duplicate problems
• [X] I have tried resolving the issue using the support portal
• [X] I have ensured my Modrinth App installation is up to date

What version of the Modrinth App are you using?

I can’t open the app so I am unable to check the exact version but I just updated so it should be the latest one

What operating systems are you seeing the problem on?

Linux

Describe the bug

When I try to open the Modrinth App, it does not open. If I try to open it through the terminal with flatpak run com.modrinth.ModrinthApp it states this: ’Gtk-Message: 21:46:58.160: Failed to load module ”xapp-gtk3-module”’

Steps to reproduce

1. Try to open Modrinth App
2. See how it fails

Expected behavior

The app should open

Additional context

I use Linux Mint 21.3 Cinnamon

[Norbiros]

Try installing xapp:

sudo apt install xapp

or:

sudo apt install xapp-sn-watcher libxapp-gtk3-module

[centuryboy774]

I'm also using Linux, specifically Fedora 40, and it works perfectly for me. While I can't offer direct help, I have a few suggestions that might be useful:

System Update: Have you updated your system recently? It might seem trivial, but sometimes outdated libraries or dependencies can cause issues.
AppImage: Have you tried using the AppImage version of the application? That's what I've been using, and it works flawlessly.

If these suggestions don't help, it's possible there might be an error in one of your commands. If you're open to it, you could consider switching to Fedora 40, as that's what I'm using, and it works without any problems. I hope you're able to resolve the issue soon!

[Alquas]

Are you using the flatpak version of the app? I am on LMDE 6 and have the same problem Maybe this is specific to Linux Mint but not sure

Try installing xapp:

sudo apt install xapp

or:

sudo apt install xapp-sn-watcher libxapp-gtk3-module

From what I was able to find online, the error message isn't related to the app stopping. and is due to the flatpak accessing the GTK3_MODULES environment variable. (You can get rid of the message by running unset GTK3_MODULES, but this doesn't fix the app not starting)

Looking at the logs, the real problem seam to be the following:

ERROR theseus_gui: Error registering deep link handler: No such file or directory (os error 2)

[twigtarsier]

Yes, I am using the flatpak version. I tried the .deb too but it is not starting either

[Alquas]

With the .deb version I get another error because of the program looking for libssl (and libcrypto) 1.1 where system package is version 3

The appimage won't start either, with yet another seamingly unrelated error:

mv: /tmp/.mount_modrin8DChMc/usr/lib/libselinux.so.1: no version information available (required by mv)

and a core dump

[twigtarsier]

ugh. Is there any temp fix for this?

[LAutomate-dev]

I'm on Fedora 40 using the flatpak and I can't get it to open either. The App Image opens, but it's a graphical nightmare.

Perhaps this is graphics-related? I think my nvidia drivers updated to 560.35.03 at the same time I updated Modrinth. Just a guess. ¯_(ツ)_/¯

[pokahs]

ugh. Is there any temp fix for this?

Just here to say that with the Modrinth 8.2 deb package, I also started get the libssl & libcrypto 1.1 missing error where system has 1.3, and I tried the AppImage. This worked until today (where I think it updated to 8.5?), so I tried installing the deb package again (the new 8.5 version).

Running it (theseus_gui in terminal) got me a segmentation fault, specifically:

src/nv_gbm.c:300: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

However, I found some random fix to this here (https://github.com/tauri-apps/tauri/issues/8462), which is to simply run it as:

WEBKIT_DISABLE_DMABUF_RENDERER=1 theseus_gui

And this fix seems to work fine for me.

I also simply changed my .desktop file for modrinth to adjust for this, by just doing:

sudo nano /usr/share/applications/theseus_gui.desktop

and then changing Exec=theseus_gui to:

Exec=env WEBKIT_DISABLE_DMABUF_RENDERER=1 theseus_gui

I know this wasn't an issue declared here, but I thought updating to 8.5 deb package and doing this might work for others, at least did for me.

[twigtarsier]

i tried the 8.5 deb and the theseus_gui is running but no modrinth is popping up sadly

[LAutomate-dev]

Can confirm 8.5 App Image is working smoothly on Fedora, but the Flatpak (which is still on 8.2) still doesn't work. Perhaps it will work again when Flatpak updates? I'll be sure to watch out for the update and test as soon as it drops.

[DexTheExplorer]

Adding WEBKIT_DISABLE_DMABUF_RENDERER=1 as an environment variable for the flatpak made the client launch perfectly on the latest release. I was even able to enable GPU acceleration, which was not possible before. OS: Fedora 40

[Legion495]

I am on Fedora too... Well the Appimage stopped working for me today - does nothing. Which is 8.8. Wanted to test some server I made for someone. Seemed to update and stopped working. And the Flatpak is even better.

[spusuf]

I am on Fedora too... Well the Appimage stopped working for me today - does nothing. Which is 8.8. Wanted to test some server I made for someone. Seemed to update and stopped working. And the Flatpak is even better.

yeah same

[CoderModeGit]

Experiencing the same issue. I'm on mint 21.3, opened the AppImage, it updated, and instead of opening the updated version, it closed and no longers opens. I have updated my system and redownloaded the AppImage, still nothing.

[anylonen]

And same issue here. Using Manjaro (Arch) and everything is updated to it's latest version. Modrinth app version (from the file name) is 0.8.8.

Getting error "Error: Error executing 'Modrinth': No such file or directory".

[Legion495]

And same issue here. Using Manjaro (Arch) and everything is updated to it's latest version. Modrinth app version (from the file name) is 0.8.8.

Getting error "Error: Error executing 'Modrinth': No such file or directory".

I think this happens if you try to run the appimage from console. I just made it executeable and tried to "run" it from the file manager.

[anylonen]

Getting error "Error: Error executing 'Modrinth': No such file or directory".

I think this happens if you try to run the appimage from console.

Tried also from the file manager (Nemo) with same results. Won't start.

[CoderModeGit]

And same issue here. Using Manjaro (Arch) and everything is updated to it's latest version. Modrinth app version (from the file name) is 0.8.8.

Getting error "Error: Error executing 'Modrinth': No such file or directory".

This also happened for me when I tried installing it from .deb, but I just thought I had installed it wrong.

[MyUsernamee]

I am also experiencing the same error after a update on Ubuntu 24.04. I have tried the flatpak, deb, and AppImage. Same error message as well

dihydromonoxide@mycomputer:~/AppImages$ ./modrinth_app.appimage Error: Error executing 'Modrinth': No such file or directory

In the flatpak version I get this error

Gtk-Message: 11:26:10.136: Failed to load module "xapp-gtk3-module" Gtk-Message: 11:26:10.174: Failed to load module "canberra-gtk-module" Gtk-Message: 11:26:10.175: Failed to load module "canberra-gtk-module"

I've attempted the aforementioned fix by running sudo apt install xapp-sn-watcher libxapp-gtk3-module but this yielded the same results.

[AncientMRG]

Just tried upgrading from the app, and it fails due to lack of priviledges. Downloaded and installed the .deb in Linux Mint 22 and app installs but gtk-update-icon-cache fails due to the space now included between Modrinth and App... I can run 'Modrinth\ App' from the terminal, but app and icon will never generate... I must manually run it everytime... happened with version Modrinth App_0.8.8_amd64.deb.

[pokahs]

Just noting I think most of the problems mentioned here recently are related to https://github.com/modrinth/code/issues/2480

Might want to check out the working builds/solutions posted there.

[elisenlebkuch]

For me it doesn't work since I'm on 0.8.7. I use Arch btw.

[855579762735]

Running Modrinth on Debian Bookworn with KDE Wayland, can confirm the Flatpak for version 0.8.2 and 0.8.7 don't even open when clicked on. I ran sudo flatpak update --commit=ee812d6fe9d492cbbd8f1f03b5bb552b264761b3d6ce07375ce7fdcceea4e4be com.modrinth.ModrinthApp in the console and it now works, but it sucks that a downgrade was required, looking forward to a fix.

[AncientMRG]

Just noting I think most of the problems mentioned here recently are related to #2480

Might want to check out the working builds/solutions posted there.

Thanks... got it to work through help in #2480

[CoderModeGit]

Also got it fixed in #2480

[noxidsoft]

On Ubuntu 24.04 LTS I was missing a library. This was a fresh OS install just yesterday, so it makes sense I hadn't picked this one up yet.

sudo apt install libfuse2t64

Now the latest AppImage file from Modrinth is working after permissions set correctly. https://modrinth.com/app

Credit: https://itsfoss.com/cant-run-appimage-ubuntu/

[ldeninski]

@twigtarsier I found what the issue is - for some reason the ModrinthApp is having issues when it connects to the d-bus accessibility toolkit. Adding NO_AT_BRIDGE=1 to the env of the application fixes it. My menu entry launch command now looks like this env NO_AT_BRIDGE=1 ModrinthApp.

[Patitotective]

What @ldeninski said works perfectly, thanks. 💯

[CrazyWolf13]

For me adding GDK_BACKEND=x11 worked. (NixOS Wayland Gnome)

[Lampe2020]

For me Modrinth crashes when trying to launch under Wayland (on Nobara 42 KDE), stating that it failed to dispatch to Wayland display (error 71, protocol error, full log below) and when adding GDK_BACKEND=x11 it opens and seems to work, but displays only black. The cursor changes when I move it, depending on where there would have been a button and where not.
I installed Modrinth using the RPM file download from the "Download options" page today, because the AppImage launched from an old version (I haven't used it in a few months, last time probably November or December last year), updated on startup, then crashed after popping up a black rectangle for a split-second.

Launch log on Wayland

lampe2020@nobara-pc:~$ ModrinthApp
Gtk-Message: 16:46:09.948: Failed to load module "appmenu-gtk-module"
Gtk-Message: 16:46:10.168: Failed to load module "appmenu-gtk-module"
Gdk-Message: 16:46:10.244: Error 71 (Protokollfel) dispatching to Wayland display.
lampe2020@nobara-pc:~$ ERROR: WebKit encountered an internal error. This is a WebKit bug.
/builddir/build/BUILD/webkitgtk-2.48.3-build/webkitgtk-2.48.3/Source/WebKit/WebProcess/Network/WebLoaderStrategy.cpp(577) : internallyFailedLoadTimerFired
ERROR: WebKit encountered an internal error. This is a WebKit bug.
/builddir/build/BUILD/webkitgtk-2.48.3-build/webkitgtk-2.48.3/Source/WebKit/WebProcess/Network/WebLoaderStrategy.cpp(577) : internallyFailedLoadTimerFired

(The next shell prompt is in the middle of the output because the main process must have exited before all the subprocesses were done outputting their error messages)

Launch log on XWayland

I can unfortunately not just start an X11 session, it immediately crashes and boots me back into the login screen. So I'm forced to use XWayland for X11 apps.

lampe2020@nobara-pc:~$ env GDK_BACKEND=x11 XDG_SESSION_TYPE=x11 DISPLAY=:0 ModrinthApp
Gtk-Message: 16:53:26.191: Failed to load module "appmenu-gtk-module"
Failed to create GBM buffer of size 1920x1080: Ogiltigt argument
lampe2020@nobara-pc:~$ 

[EDIT]: I can get it to display its content by SSHing into my own computer and launching it from there:

ssh -X localhost 'env GDK_BACKEND=x11 XDG_SESSION_TYPE=x11 ModrinthApp'

Modrinth itself renders a bit blurry for me that way. To get Minecraft itself to connect directly to XWayland and not to SSH's X tunnel (to reduce overhead), I needed to add DISPLAY=:0 to "Default instance options → Environmental variables". Doing that raised my FPS from barely 10 to a stable 70+.