Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flatpak version of the launcher prevents the game from launching with a Wayland-first GLFW native. #67

Open
LemonHeadOnGit opened this issue Jul 23, 2024 · 2 comments

Comments

@LemonHeadOnGit
Copy link

LemonHeadOnGit commented Jul 23, 2024

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

@zefr0x
Copy link

zefr0x commented Jul 31, 2024

Is this a duplicate of #64 ?

Are you using the Nvidia drivers?

@LemonHeadOnGit
Copy link
Author

Is this a duplicate of #64 ?

Are you using the Nvidia drivers?

Hi!
I have tried running with the environment variable:
__GL_THREADED_OPTIMIZATIONS=0
but the problem still exists.

I also forgot to mention that my error trace above specifically happens with the VulkanMod, but since then I have also noticed that it happens with Sodium, regardless of whether I have __GL_THREADED_OPTIMIZATIONS set.

Looking further into it, other Flatpak applications with my setup seem to have troubles working with Vulkan. And yes, I am using the Nvidia non-open drivers, but I have also tried with the open kernel variant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants