Linux-specific performance, graphical, or crashing issues [MEGA-ISSUE]

Please confirm the following.

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

What version of the Modrinth App are you using?

0.9.0

What operating systems are you seeing the problem on?

Linux

Describe the bug

I use an Nvidia GPU and Arch Linux. The app just updated to 0.9.0, but immediately I noticed that it's unusably slow. When interacting with it, like moving the cursor from one button to another, it freezes for about a second, although animations look smooth afterwards (if I stop moving). I see no errors or logs anywhere.
The GPU is relevant because, as with previous versions and even other apps, the app crashes on startup if run normally, so it needs the workaround of setting WEBKIT_DISABLE_DMABUF_RENDERER=1 (or WEBKIT_DISABLE_COMPOSITING_MODE=1), but that workaround worked decently in previous versions, so something changed now.
The Modrinth app seems to account for software rendering by providing the "advanced rendering" toggle, but even though turning it off is supposed to help with this, it doesn't improve the situation.

same thing happening to me after updating. extremely annoying issue

I'm also facing this issue on Arch with version 0.9.0 (modrinth-app-bin, aur). Although, I don't have a NVIDIA GPU; rather, my system uses an Intel iGPU. I've tried turning off Advanced rendering, however it doesn't resolve the issue.

2024-12-24.09-13-20.mp4

I can reproduce this issue. Compiling from source and using this binary also doesn't help.

This issue is probably caused by WebKit - web view used by tauri on Linux. The tauri team is working on other alternatives like cef (chromium) or servo. For now we can only way and try to find bottlenecks and optimize them if we can.

I'm running Manjaro and after updating I now get this when I run version 0.9.0

Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

** (ModrinthApp:2121): WARNING **: 19:50:50.282: atk-bridge: get_device_events_reply: unknown signature

this is what i have tried and still getting

Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

** (ModrinthApp:12167): WARNING **: 20:49:54.234: atk-bridge: get_device_events_reply: unknown signature

one.txt

I have a similar problem but with a AMD GPU, previous version seemed to run perfectly.

I have a similar problem but with a AMD GPU, previous version seemed to run perfectly.

Depending on how you installed it, you might be unintentionally still using the workaround I mentioned. For me, /usr/bin/modrinth-app is a shell script that sets WEBKIT_DISABLE_DMABUF_RENDERER=1 and runs the actual app executable in /opt/, presumably to prevent it from crashing for Nvidia users. Can you try running the app directly, or changing that variable to 0 instead of 1?

I have a similar problem but with a AMD GPU, previous version seemed to run perfectly.

Depending on how you installed it, you might be unintentionally still using the workaround I mentioned. For me, /usr/bin/modrinth-app is a shell script that sets WEBKIT_DISABLE_DMABUF_RENDERER=1 and runs the actual app executable in /opt/, presumably to prevent it from crashing for Nvidia users. Can you try running the app directly, or changing that variable to 0 instead of 1?

That fixes it for me, thanks.

Manually compiling and setting WEBKIT_DISABLE_DMABUF_RENDERER=0 completly fixes this issue for me.

That fixes it for me, thanks.

Welp, that confirms the idea that this is a problem for Nvidia+Linux users, since we can't change that to 0 or it will crash on startup

Arch users can try the modrinth-app-segfault-fix-bin AUR package for a quick fix, I've been using it myself ever since 0.8.0. Users on other distros can try setting these env variables:

export WEBKIT_DISABLE_DMABUF_RENDERER=1
export LIBGL_ALWAYS_SOFTWARE=1
export GDK_BACKEND=x11

I am also having this issue (on pop os with Nvidia gpu), hope this gets fixed soon.

Manually compiling and setting WEBKIT_DISABLE_DMABUF_RENDERER=0 completly fixes this issue for me.

Is this something we can edit in GH actions to generate a working build?

hey! i have the same issue as in #7350 , so I have the Too many requests - errors in modrinth. do we have a fix for that in version 0.21.4 on linux 7.1.13-2-MANJARO? thx for helping

After the latest update (specifically on the AUR), this issue seems to have been fixed. (App ver 0.21.4)
However the flatpak still has the issue.

After the latest update (specifically on the AUR), this issue seems to have been fixed. (App ver 0.21.4)
However the flatpak still has the issue.

That's good, but does the .deb or .AppImage still have the bug ?

After the latest update (specifically on the AUR), this issue seems to have been fixed. (App ver 0.21.4)
However the flatpak still has the issue.

That's good, but does the .deb or .AppImage still have the bug ?

Not sure, I'm not using debian and the AppImage never works for me anyway.

After the latest update (specifically on the AUR), this issue seems to have been fixed. (App ver 0.21.4)
However the flatpak still has the issue.

That's good, but does the .deb or .AppImage still have the bug ?

Not sure, I'm not using debian and the AppImage never works for me anyway.

Okay, because my flatpak got smoother but, it now takes 8 minutes or more to launch an instance because modrinth all indexes all of my instances (even the ones with 400 mods) and it does it every time.

I am not seeming to have the issue anymore on flatpak

Nowadays, I only use one environment flag WEBKIT_DISABLE_DMABUF_RENDERER=1 for the Flatpak version to work

Below is the full .desktop launch argument

/usr/bin/flatpak run --branch=stable --arch=x86_64 --env=WEBKIT_DISABLE_DMABUF_RENDERER=1 --command=modrinth-app com.modrinth.ModrinthApp

This still doesn't fix the app performing slowly, but it has gotten slightly more performant over updates. I am glad to say the crashes have largely gone away. My main concern is how bulk operations are very sluggish (removing/updating several mods), which drives me to do them externally; I only use the App to update individual mods and launch the game.

The DEB package seems to launch fine without any extra flags needed. Though it's still slow like the Flatpak.

I'm currently doing some experiments with Tauri CEF which runs better on Linux. General performance etc. is quite promising, but ~~somehow Minecraft Login is broken~~, I also had not managed to package it as a flatpak yet. Here is my fork.

@Zoriot

@Zoriot, your CEF rendering engine made the app work very smoothly for me! (Zorin OS, NVIDIA Drivers)
Since Tauri normally uses WebKitGTK on Linux, I'm wondering whether Modrinth has any plans to adopt Tauri's CEF runtime once it becomes stable enough for production use.

Glad that it make it smooth for you, same like for me.

Afaik they are currently doing some testing their own, that was written somewhere. So likely they will adopt it once it's suitable enough.

I've found another Linux related issue, when I try to export this specific modpack to a .mrpack file, it gives me a Unix-style relative path error.

2026-10-09.09-05-13.mp4

Some good news ! I'm on Arch Linux & running it through the AUR, and while the app wouldn't even open for months, it now works perfectly w/ all of its features (no stuttering, instances "more actions" button can now open w/o crashing the app).

Currently on 0.22.0, but I'm a little hesitant to update in case it breaks again, will tell you if anything goes wrong.

@Y4k3d0

@Y4k3d0 I just pushed modrinth-app 0.22.0 to [extra], it would be very interesting to know if that also works for you.

Same here. I just downloaded the 0.22.1 AppImage on Fedora 44 and it finally opens, instead of crashing.

The update to 0.22.1 fixed the crashing for me as well on CachyOS, although I still need to run it with WEBKIT_DISABLE_DMABUF_RENDERER=1 for it to work.

Navigation Menu

Repository navigation

Linux-specific performance, graphical, or crashing issues [MEGA-ISSUE] #3057

Please confirm the following.

What version of the Modrinth App are you using?

What operating systems are you seeing the problem on?

Describe the bug

281 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Linux-specific performance, graphical, or crashing issues [MEGA-ISSUE] #3057

Description

Please confirm the following.

What version of the Modrinth App are you using?

What operating systems are you seeing the problem on?

Describe the bug

Activity

juniorbutyeah commented on Dec 24, 2024

snipcola commented on Dec 24, 2024

Norbiros commented on Dec 24, 2024

Phill3005 commented on Dec 24, 2024

Phill3005 commented on Dec 24, 2024

Faustvii commented on Dec 24, 2024

malucard commented on Dec 24, 2024

Faustvii commented on Dec 24, 2024

Norbiros commented on Dec 24, 2024

malucard commented on Dec 24, 2024

cranberry3148 commented on Dec 24, 2024

MinestoneBlock commented on Dec 24, 2024

Geometrically commented on Dec 25, 2024

281 remaining items

NIFOXLI commented on Sep 25, 2026

HungryBoy02 commented on Sep 25, 2026

marinstanislas01-cloud commented on Sep 26, 2026

HungryBoy02 commented on Sep 26, 2026

marinstanislas01-cloud commented on Sep 26, 2026

Herjiberb commented on Sep 30, 2026

SalmonSnaked commented on Oct 1, 2026

Zoriot commented on Oct 1, 2026

SalmonSnaked commented on Oct 2, 2026

Zoriot commented on Oct 4, 2026

GG-Man1 commented on Oct 9, 2026

Y4k3d0 commented on Oct 29, 2026

tippfehlr commented on Oct 30, 2026

bangetto commented on Oct 30, 2026

Vantikay commented on Nov 2, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions