crashing on startup

[sammywammythewam]

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?

0.7.1

What operating systems are you seeing the problem on?

Linux

Describe the bug

When I try to launch the latest version of the app, it shows up on the system monitor for a few seconds before ultimately crashing.

Steps to reproduce

open app

Expected behavior

No response

Additional context

No response

[AncientMRG]

Tried opening up the app, it started auto updating, then crashed due to permissions. Downloaded the latest version from the web site a and got 'Modrinth App_0.9.0-1_amd64 (deb package) for Linux Mint 22, and after installation, the app tries to auto update again with the following debug code:

invalid updater binary format.

Please help/advise?

[CrudeWax]

Also experiencing "invalid updater binary format" on the deb version, any way this can be solved?

[sammywammythewam]

i

[sammywammythewam]

i didn’t mean to close

[pawlrip]

I am having the same issue on Pop!_OS 22 with the Modrinth App_0.9.0-1_amd64.deb as well. It would be nice if this issue could be reopened if no solution has been found.

[jannispkz]

same issue here on linux mint (newest)

[sammywammythewam]

i can reopen now i think

[brunoflavio-com]

Tried opening up the app, it started auto updating, then crashed due to permissions. Downloaded the latest version from the web site a and got 'Modrinth App_0.9.0-1_amd64 (deb package) for Linux Mint 22, and after installation, the app tries to auto update again with the following debug code:

invalid updater binary format.

Please help/advise?

Same behaviour here. Although I was in 0.8.9 deb version initially (permissions error), then upgraded to 0.9.0-1 and get invalid binary format.

Was working fine 2 days ago.

My OS is Ubuntu 24.04.1 LTS on a Dell Inc. XPS 9315.

Had to fallback to AppImage 0.9.0, though not ideal as it can't run my pre-game hooks.

Let me know if there's any other info that may be useful (there's no effect to adding --help or --verbose to the executable, so I couldn't get additional output).

[julianflash11]

... the app tries to auto update again with the following debug code: invalid updater binary format. Please help/advise?

Same behaviour here. Although I was in 0.8.9 deb version initially (permissions error), then upgraded to 0.9.0-1 and get invalid binary format.

Was working fine 2 days ago.

My OS is Ubuntu 24.04.1 LTS on a Dell Inc. XPS 9315.

Had to fallback to AppImage 0.9.0, though not ideal as it can't run my pre-game hooks.

Let me know if there's any other info that may be useful (there's no effect to adding --help or --verbose to the executable, so I couldn't get additional output).

Same issue here, same OS.

[jannispkz]

Workaround for me was rollback to before I first opened the app because at first it showed a permission error. After that popped up I closed the app and then sudo opened it which fixed the issue

[pawlrip]

I got it to work by going to the actions of this repository, the newest Modrinth App build (fix lint, labrinth crash), downloading the ubuntu-22.04 zip and installing the contained deb. I don't know whether this still contains bugs, but I hope they will soon publish a working version like this one on the modrinth website.

[AncientMRG]

I got it to work by going to the actions of this repository, the newest Modrinth App build (fix lint, labrinth crash), downloading the ubuntu-22.04 zip and installing the contained deb. I don't know whether this still contains bugs, but I hope they will soon publish a working version like this one on the modrinth website.

Tried the Fix Lint, downloading the ubuntu-22.04.zip, and still got the same, invalid updater binary format.

[AncientMRG]

Workaround for me was rollback to before I first opened the app because at first it showed a permission error. After that popped up I closed the app and then sudo opened it which fixed the issue

Tried it, but the app keeps auto-updating up to the invalid updater binary format

Lost the app for the foreseeable future until they come up with a fix... I guess, no Modded Minecraft for Christmas... a bummer.

[jannispkz]

Workaround for me was rollback to before I first opened the app because at first it showed a permission error. After that popped up I closed the app and then sudo opened it which fixed the issue

Tried it, but the app keeps auto-updating up to the invalid updater binary format

Lost the app for the foreseeable future until they come up with a fix... I guess, no Modded Minecraft for Christmas... a bummer.

You can always get in by disabling your internet when opening the app if you really need to get in because something goes wrong when applying an update which is basically a loop since the app forces it to install

[pawlrip]

I got it to work by going to the actions of this repository, the newest Modrinth App build (fix lint, labrinth crash), downloading the ubuntu-22.04 zip and installing the contained deb. I don't know whether this still contains bugs, but I hope they will soon publish a working version like this one on the modrinth website.

Tried the Fix Lint, downloading the ubuntu-22.04.zip, and still got the same, invalid updater binary format.

Be aware that there now is a new build (v0.9.1 fixes). The older one doesn't work anymore for me as well.

[AncientMRG]

I got it to work by going to the actions of this repository, the newest Modrinth App build (fix lint, labrinth crash), downloading the ubuntu-22.04 zip and installing the contained deb. I don't know whether this still contains bugs, but I hope they will soon publish a working version like this one on the modrinth website.

Tried the Fix Lint, downloading the ubuntu-22.04.zip, and still got the same, invalid updater binary format.

Be aware that there now is a new build (v0.9.1 fixes). The older one doesn't work anymore for me as well.

I don´t know, maybe I'm doing the unistall wrong or leaving something behind... tried the 12/25 fix... same result... invalid updater binary format It keeps auto-updating when opening, no matter what I do... why it keeps auto updating the app if its the latest version? Anyway... still stuck...

[brunoflavio-com]

I got it to work by going to the actions of this repository, the newest Modrinth App build (fix lint, labrinth crash), downloading the ubuntu-22.04 zip and installing the contained deb. I don't know whether this still contains bugs, but I hope they will soon publish a working version like this one on the modrinth website.

Tried the Fix Lint, downloading the ubuntu-22.04.zip, and still got the same, invalid updater binary format.

Be aware that there now is a new build (v0.9.1 fixes). The older one doesn't work anymore for me as well.

I don´t know, maybe I'm doing the unistall wrong or leaving something behind... tried the 12/25 fix... same result... invalid updater binary format It keeps auto-updating when opening, no matter what I do... why it keeps auto updating the app if its the latest version? Anyway... still stuck...

Just confirming that you're not alone on this.

0.9.0-2 continues to display the invalid updater format for me, and rolling back to the 0.8.9 version I had before will not work as it doesn't recognize the migration.

I'll wait a few more days to see if there's a solution that doesn't involve deleting the app data.

[brunoflavio-com]

Update: theres a new deb available on the website 0.9.2 - installed it from that source and the app just started!

https://modrinth.com/app

[Prospector]

Should be fixed

[sammywammythewam]

nope, mines still broken

[Dkr0l]

Still an issue, anyone working on this?

[sammywammythewam]

Now on ubuntu, it randomly broke again with the same error. I was so annoyed that i hadnt thought about this before, but i just did sudo ap

[sammywammythewam]

omg wait

[sammywammythewam]

i did sudo apt remove modrinth-app

[sammywammythewam]

lol

[Warentan]

Now having the same issue, different reason. Trying to run the app image or DEB installation now returns Could not create GBM EGL display: EGL_NOT_INITIALIZED. Aborting... Friendly reminder to update your OS software if you havent; some things can break and become obsolete causing applications to not work when your PC is outdated.

EDIT: RESOLVED by updating Ubuntu software and restarting, try sudo apt update

[beowuff]

I'm getting this as well. Unfortunately, the appimage is also unusable due to lag. :(

[sbarrack]

I don't have issues when configuring my machine to only run on the Nvidia gpu. It crashes on startup with @Warentan's error if I reenable Intel graphics to use them together or if I switch to Wayland. https://github.com/modrinth/code/issues/1157#issuecomment-2423335219 allows for the app to work in the situation where it does crash but I get 1 fps 😅

[Pocapka]

Doesn't work for me as well. It appears on panel for a few seconds and then crashes. Could not create GBM EGL display: EGL_SUCCESS. Aborting... I'm using the AppImage version and I'm on Fedora. Update: Tried the unoffical flatpak, crashes as well. It's not just the appimage

[KDPryor]

I'm using the .deb and getting the invalid updater binary format error as well. I was on a previous version (forget which one) and getting the error. I installed the latest .deb and it fixed it for a while but now I'm getting the error again.