You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon some investigation this is definitely not an issue with the launcher but with fabric. Launching the game in any other way does not fail due to missing glfw libraries
Also getting the same issue, except that for me it definitely is an UltimMC issue, and not fabric or anything like that.
Operating System
Linux (amd64) version 5.10.126-std-def-alt1
Description of bug
When trying to launch a completely fresh instance without fabric/forge/..., Minecraft always crashes on every version starting with 1.13 (starting with the first 1.13 snapshot specifically – 17w43a).
Things I've tried
Launching a version prior to 1.13 – worked.
Reinstalling UltimMC from scratch – didn't help.
Installing MultiMC instead – it worked completely fine on the same PC.
Copying the instance folder from MultiMC – didn't help.
Replacing the "libraries" folder with the one from MultiMC – didn't help.
Changing the LWJGL version in an UltimMC instance to a newer one – didn't work, it just gets reset to 3.2.2 build 10.
Installing UltimMC on a different Windows PC – worked fine.
Suspected cause
17w43a is the snapshot, in which there were "Game library updates: Upgraded to LWJGL 3.1.2". Since from my understanding of the crash log, the game crash has something to do with glfw, which is in the lwjgl folder in libraries, I'm pretty sure that the issue is somehow related to it.
Operating System
Linux
Description of bug
The moment minecraft tries to initialise the window, it crashes due to
crash-2022-10-17_20.58.47-client.txt
Attached file is the crash report when running a modded instance I tried to use, stripped from all the mods
Things I've tried
lwjgl
from the package managerSteps to reproduce
Run any instance
Suspected cause
I'm pretty sure it's a problem with my setup because no matter the instance I try to run, it always fails to this error
This issue is unique
The text was updated successfully, but these errors were encountered: