Minecraft launcher crashed in Debian


#1

I installed minecraft with the normal snap install via the terminal.
It installs, and when I log in it downloads the latest files, but when finished I get an error message.
No idea what to do.
This is my error message:

---- Minecraft Crash Report ----
// Quite honestly, I wouldn’t worry myself about that.

Time: 9/1/18 10:10 PM
Description: Initializing game

java.lang.IllegalStateException: GLFW error 65543: GLX: Failed to create context: BadValue
at cgc.b(SourceFile:218)
at org.lwjgl.glfw.GLFWErrorCallbackI.callback(GLFWErrorCallbackI.java:36)
at org.lwjgl.system.JNI.invokePPPP(Native Method)
at org.lwjgl.glfw.GLFW.nglfwCreateWindow(GLFW.java:1649)
at org.lwjgl.glfw.GLFW.glfwCreateWindow(GLFW.java:1827)
at cgc.(SourceFile:99)
at cgb.a(SourceFile:79)
at cfs.am(SourceFile:439)
at cfs.a(SourceFile:380)
at net.minecraft.client.main.Main.main(SourceFile:144)

A detailed walkthrough of the error, its code path and all known details is as follows:

– Head –
Thread: Client thread
Stacktrace:
at cgc.b(SourceFile:218)
at org.lwjgl.glfw.GLFWErrorCallbackI.callback(GLFWErrorCallbackI.java:36)
at org.lwjgl.system.JNI.invokePPPP(Native Method)
at org.lwjgl.glfw.GLFW.nglfwCreateWindow(GLFW.java:1649)
at org.lwjgl.glfw.GLFW.glfwCreateWindow(GLFW.java:1827)
at cgc.(SourceFile:99)
at cgb.a(SourceFile:79)
at cfs.am(SourceFile:439)

– Initialization –
Details:
Stacktrace:
at cfs.a(SourceFile:380)
at net.minecraft.client.main.Main.main(SourceFile:144)

– System Details –
Details:
Minecraft Version: 1.13.1
Operating System: Linux (amd64) version 4.9.0-8-amd64
Java Version: 1.8.0_171, Oracle Corporation
Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 126805272 bytes (120 MB) / 268435456 bytes (256 MB) up to 2147483648 bytes (2048 MB)
JVM Flags: 8 total; -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
Launched Version: 1.13.1
LWJGL: 3.1.6 build 14
OpenGL: NO CONTEXT
GL Caps:
Using VBOs: Yes
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs:
Current Language: ERROR NullPointerException: null
Profiler Position: N/A (disabled)
CPU:


#2

Is the launcher snap connected to the opengl interface?


#3

No idea, I installed minecraft via snap, and clicked open in Applications/Games and the launcher is called Minecraft Launcher. All other 3d graphics are working on my machine, blender, houdini, substancepainter, so I’m not sure there is a driver issue? How can I connect OpenGL to the Minecraft launcher? :slight_smile:


#4

Refer the following article for information regarding snapd’s security confinement and interfaces:

This shouldn’t be the cause though as the opengl interface is an auto-connect interface, and should be connected by default upon install.


#5

Ok, so basically its just broken. I’ll try and reinstall and see if it works, thanks anyways! :slight_smile:


#6

reinstall will most likely just get you the same result if you do not research the actual cause …

snap interfaces minecraft

should show you if all interfaces are connected correctly … if not, use the snap connect command to connect them.


#7

Ok nice! This is what I have on the OpenGL row:
:opengl cncra,mailspring,minecraft

So I guess its connected right? Could it be something else?


#8

Yes, as expected. So the cause would be something else


#9

indeed, it is likely not the interface then. watch syslog or journalctl while you start the app and look for any errors.

Also what graphics card do you use and do you use a distro provided driver or anything you installed from a third party location (amdgpu upstream drivers come to mind here, they seem to install in /opt which snapd does not take into account at all currently)