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
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?
Modrinth App 0.9.3 Linux 25.0.0
What operating systems are you seeing the problem on?
Linux Manjaro
Describe the bug
Greetings,
Upon launching my instance I get the following message : /home/<REMOVED>/.local/share/ModrinthApp/meta/libraries/org/lwjgl/lwjgl-glfw-natives-linux-arm64/3.3.1-lwjgl.1/lwjgl-glfw-natives-linux-arm64-3.3.1-lwjgl.1.jar does not exist.
What's strange is that I'm not running the app on ARM, moreover I do have the required library located at /home/<REMOVED>/.local/share/ModrinthApp/meta/libraries/org/lwjgl/lwjgl-glfw/3.3.1.
I don't know why but the app is looking for the wrong library, at the wrong location.
Best regards.
Steps to reproduce
Launch the instance
Expected behavior
Run minecraft successfully
Additional context
No response
The text was updated successfully, but these errors were encountered:
Please confirm the following.
What version of the Modrinth App are you using?
Modrinth App 0.9.3 Linux 25.0.0
What operating systems are you seeing the problem on?
Linux Manjaro
Describe the bug
Greetings,
Upon launching my instance I get the following message :
/home/<REMOVED>/.local/share/ModrinthApp/meta/libraries/org/lwjgl/lwjgl-glfw-natives-linux-arm64/3.3.1-lwjgl.1/lwjgl-glfw-natives-linux-arm64-3.3.1-lwjgl.1.jar does not exist
.What's strange is that I'm not running the app on ARM, moreover I do have the required library located at
/home/<REMOVED>/.local/share/ModrinthApp/meta/libraries/org/lwjgl/lwjgl-glfw/3.3.1
.I don't know why but the app is looking for the wrong library, at the wrong location.
Best regards.
Steps to reproduce
Launch the instance
Expected behavior
Run minecraft successfully
Additional context
No response
The text was updated successfully, but these errors were encountered: