This process used to work, but at some point during the past month or so the game would consistently fail to load with a GLFW native that prefers Wayland over X11 (pretty much GLFW 3.4+).
While this isn't necessarily an issue that makes the game unplayable in any way, it does mean that if you do have such a set up the game is unplayable.
The crashing point is this trace:
java.lang.IllegalStateException: Failed to initialize GLFW, errors: GLFW error during init: [0x10008]Wayland: Failed to connect to display
at com.mojang.blaze3d.platform.GLX._initGlfw(SourceFile:77)
at com.mojang.blaze3d.systems.RenderSystem.initBackendSystem(SourceFile:509)
at fgo.<init>(SourceFile:502)
at net.minecraft.client.main.Main.main(SourceFile:239)
at org.prismlauncher.launcher.impl.StandardLauncher.launch(StandardLauncher.java:100)
at org.prismlauncher.EntryPoint.listen(EntryPoint.java:129)
at org.prismlauncher.EntryPoint.main(EntryPoint.java:70)
The game does however function as normal with the custom native in the non-flatpak version of the launcher.
The above issue is based off of accounts from this issue: Admicos/minecraft-wayland#64, as well as experiences of my own
Edit: Additionally, the OP and I share the same DE: KDE Plasma
This process used to work, but at some point during the past month or so the game would consistently fail to load with a GLFW native that prefers Wayland over X11 (pretty much GLFW 3.4+).
While this isn't necessarily an issue that makes the game unplayable in any way, it does mean that if you do have such a set up the game is unplayable.
The crashing point is this trace:
The game does however function as normal with the custom native in the non-flatpak version of the launcher.
Edit: Additionally, the OP and I share the same DE: KDE Plasma