Launching an instance with patched GLFW-Wayland still calls XWayland, only during launch about prismlauncher HOT 6 CLOSED

Your Minecraft.log shows the GPU info queried by Prism Launcher using glxinfo.

glxinfo will communicate with your X server's socket (in this case XWayland)

You could uninstall that tool to prevent Prism Launcher from using it

from prismlauncher.

@nokia8801, considering that this seems like an issue in glxinfo, and the fact that https://forums.opensuse.org/t/where-to-report-xwayland-crash-the-cause-matters-right/172543/2 appears to demonstrate that this might well continue to be a problem, are you certain that this issue has been remediated?

I never had crashes or anything like that. I try to keep my system use native Wayland wherever possible and seeing the XWayland process pop up while launching an instance made me investigate what the problem could be. As both the GUI and the launched Minecraft instance run natively over Wayland, I was curious why XWayland was called at all.

As demonstrated above, glxinfo was being used to get info about my GPU, which itself relies on X, which runs over XWayland since I'm on a Wayland session. Removing the mesa-utils packages which included glxinfo fixed the problem. Now when launching an instance no XWayland process pops up.

Although I might reopen this issue cause enabling MangoHud also results in the XWayland process popping up. Without MangoHud and glxinfo, no XWayland process visible.

from prismlauncher.

Prism Launcher queries information about your GPU using glxinfo. Perhaps that is the culprit here

from prismlauncher.

I doubt it. My system is pretty much Wayland only, from the variables to the apps.

I forgot to add the logs but here they are.

PrismLauncher-0.log
Minecraft.log

from prismlauncher.

You were right. Removing mesa-utils which included glxinfo fixed it. No XWayland process popped up. Just running glxinfo in a terminal triggers it too. Bit weird that a Mesa utility of all things relies on X these days.

Maybe Prism Launcher can use another tool to query GPU info? Since Lutris requires mesa-utils for me.

from prismlauncher.

#2032 (comment)

@nokia8801, considering that this seems like an issue in glxinfo, and the fact that https://forums.opensuse.org/t/where-to-report-xwayland-crash-the-cause-matters-right/172543/2 appears to demonstrate that this might well continue to be a problem, are you certain that this issue has been remediated?

from prismlauncher.