You are not logged in.
h938fhf398hf98hf3w98hfew34
Last edited by 16bt2 (2026-05-18 02:49:55)
Offline
You've tried other games besides Doom (2016) right?
Offline
You've tried other games besides Doom (2016) right?
Yes. I tested mainly with Doom 2016, because it's a game I was playing before and knew for sure it was working flawlessly. I can't get a single game to launch through proton. Every game I tested exhibits the same behavior, too
Offline
Interesting. I would assume this is a Steam regression because even across distros, packaging methods (native vs flatpak), Steam uses a runtime that it pulls on first launch. I've had this issue before but it's always been resolved by restarting Steam. Try installing supertuxkart and seeing if that runs properly under your system. I'd also try using Steam beta if you haven't already, you can opt into it using the Steam settings.
Offline
Interesting. I would assume this is a Steam regression because even across distros, packaging methods (native vs flatpak), Steam uses a runtime that it pulls on first launch. I've had this issue before but it's always been resolved by restarting Steam. Try installing supertuxkart and seeing if that runs properly under your system. I'd also try using Steam beta if you haven't already, you can opt into it using the Steam settings.
Thanks for the suggestions! I forgot to mention in the OP, but linux native games are working perfectly fine on steam (as is super tux kart).
I also tried using the steam beta, but the issue persists ![]()
Offline
This makes perfect sense since they aren't running via WINE/Proton, which appears to be the primary issue. I'm honestly at a loss other than that however. The fact you've reinstalled and tried different issues is the odd thing, because driver versions across distros will vary. Have you tried Xorg?
Last edited by cmt (2025-05-30 04:13:21)
Offline
Sounds like one of the multiple Xwayland regression in mutter 48.3
• https://gitlab.gnome.org/GNOME/mutter/-/issues/4138
Arch mutter pkgver -2 addresses one of them
• https://gitlab.archlinux.org/archlinux/ … /issues/12
but a 'proper' fix landed upstream:
• https://gitlab.gnome.org/GNOME/mutter/- … uests/4466
There will likely be a mutter pkgver -3 or an upstream microrelease.
Offline
This makes perfect sense since they aren't running via WINE/Proton, which appears to be the primary issue. I'm honestly at a loss other than that however. The fact you've reinstalled and tried different issues is the odd thing, because driver versions across distros will vary. Have you tried Xorg?
Well, I did make sure to get the most up to date nvidia drivers, even when testing with ubuntu (looking back, that might've been a mistake). Not sure if they were the exact same version, but they were all 570 at least. As for x11, just tried one more time to be sure, but the same thing happens
Sounds like one of the multiple Xwayland regression in mutter 48.3
• https://gitlab.gnome.org/GNOME/mutter/-/issues/4138
Arch mutter pkgver -2 addresses one of them
• https://gitlab.archlinux.org/archlinux/ … /issues/12
but a 'proper' fix landed upstream:
• https://gitlab.gnome.org/GNOME/mutter/- … uests/4466
There will likely be a mutter pkgver -3 or an upstream microrelease.
Oh, thanks, that makes a lot of sense! But if that's my issue, would I still be having problems even when using x11?
Offline
Well, I feel dumb... I was missing lib32-gnutls. installing it fixed the issue. (still confused on why I had the same issue on Fedora and Ubuntu, and why it suddenly stopped working a few days ago, but I guess it doesn't matter)
Thanks cmt and tekstryder for helping me troubleshoot!
Offline
Ha. I admittedly only saw Steam freeze + Wayland + Gnome in your post and went right to the current hot mutter issue without reading your details. Glad it's sorted.
Offline