code
code copied to clipboard
Segfault on start (AppImage 0.7.1)
Describe the bug
Modrinth launcher 0.7.1 (AppImage) segfaults on start. 0.6.3 still works fine.
Steps to reproduce
Start the Modrinth launcher 0.7.1 AppImage.
Expected behavior
A new window appears where the launcher shows stuff.
System information
OS: Parrot Security 6.0 (Debian-based, GNU/Linux)
Kernel: 6.5.0-13parrot1-amd64 (2023-12-19)
GPU: NVIDIA GeForce GTX 1060 6GB (drivers 525.147.05-4~deb12u1)
Additional context
Log:
$ ./modrinth-app_0.7.1_amd64.AppImage
EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
Segmentation fault
I do have 2 monitors if that's relevant.
If this is an NVIDIA issue, please provide a flag to use alternate ways of rendering. Something like --unsupported-gpu or --no-hardware-accel, depending on what the problem actually is.
Same problem here. Do you know where I can find the older appimage versions?
Can replicate on 0.7.1 & 0.7.2. 0.6.3 does not have this issue.
If you're looking for how to download a historical version, take the appimage link from the website (won't link in case it goes stale) and change the version numbers in it.
Can vouch for this, although it didn't do this 2 days ago
Back on my home machine, not the crappy Intel laptop I had on holiday, and can confirm it works. I think my Linux install I had with me to run on the laptop was missing some video drivers as I created my system with an Nvidia GPU (so Nvidia drivers) and the laptop didn't have either
This issue still persists. Current version 0.8.5 doesn't work, but 0.8.2 works fine. Latest Fedora 40. Same error on 2 laptops, one on Intel gpu only, second laptop has Intel+Nvidia. Both the same error.
$ ./Modrinth\ App_0.8.5_amd64.AppImage
Cannot get default EGL display: EGL_SUCCESS
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
Segmentation fault (core dumped)
Have you tried starting Modrinth App with WEBKIT_DISABLE_COMPOSITING_MODE=1?
with WEBKIT_DISABLE_COMPOSITING_MODE=1 it doesn't work as well. Tried under Wayland and X11. Same error