This is where the problem seems to be listed, and it has a fix, but I don’t understand what the fix is asking me to do specifically, what file to edit, where to paste this in?
Please 42 is now an open release, yet this still is an issue. How do I get this fixed?
i now managed to open steam for the first time ,
after uninstalled/Removing both NVIDIA driver and the intel one ..
than installed the NVIDIA driver after steam updated
rebooted ,and now it launches
We're still investigating this, but in the meantime, setting the environment variable __GL_CONSTANT_FRAME_RATE_HINT=3 should work around it without having to disable the whole driver.
Can someone tranlaste this fix. I saw it posted about above here in this forum, but no one says exactly what to do. What file to edit and add this. What exactly to do. In simple english?
For me with AMD, the Steam version from rpmfusion only starts if I use __GL_CONSTANT_FRAME_RATE_HINT=3 steam, so it looks like the issue is the same as with NVIDIA.
In Plasma (I’m sure it’s fairly close for GNOME), right click your shortcut to Steam, and click Edit Application. In the “Environment Variables” field, paste in __GL_CONSTANT_FRAME_RATE_HINT=3
I’m not entirely familiar with this bug, but it sounds like there’s something else going on for a NVIDIA proprietary driver env to affect anything outside of that.
If Steam or something else does a check for that specific env regardless of GPU and then does something based on it, it sounds like understanding that something could hint to a different thing causing the issue (I’d search on Valve bug trackers with that env).
Could also be something like that large text string causing a race condition or extra spacing in a command syntax somewhere; Flatpak and Steam do a lot of stuff (especially pressure-vessel stuff)
As far as I know, since the bug isn’t NVIDIA-specific but also affects AMD, it impacts any card using 32-bit libraries (glibc/libglvnd). Setting __GL_CONSTANT_FRAME_RATE_HINT=3 then provides a workaround until RPM Fusion releases fixes.
Where did that __GL_CONSTANT_FRAME_RATE_HINT env originally come from? I didn’t see it on NVIDIA’s OGL driver envs notes, but that __GL beginning I’ve only seen related to NVIDIA drivers.
The name itself also doesn’t hint at anything 32-bit or library-related. Looking at it I’m thinking it’s something with Vsync timings
What I understand is that __GL_CONSTANT_FRAME_RATE_HINT=3 disables the faulty code path in the entire 32-bit libGL library, activating an alternative branch that circumvents the issues Fedora 42 has with 32-bit libglvnd/glibc. In short, it’s a hack. But I might be wrong.