For reference, even Deban Stable has been at glibc 2.31 or newer for three major versions now, and another major version is on its way this year. I don't think this will affect many people.
this post was submitted on 22 Apr 2025
206 points (100.0% liked)
Linux Gaming
18042 readers
532 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
2.31 was released on 2020-02-01.
That's surprisingly new. Wonder what causes the incompatibility
The changelog for 2.31 is here:
https://sourceware.org/legacy-ml/libc-announce/2020/msg00001.html
Latest version of glibc is 2.41, released 2025-01-30. That puts 2.31 at least 10 releases behind. That version is quite outdated. There are numerous security and bug fixes in 2.31 alone, with each newer release also fixing some as well.
This might be the reason for requiring glibc 2.31 and newer:
Security related changes:
CVE-2019-19126: ld.so failed to ignore the LD_PREFER_MAP_32BIT_EXEC environment variable during program execution after a security transition, allowing local attackers to restrict the possible mapping addresses for loaded libraries and thus bypass ASLR for a setuid program. Reported by Marcin Kościelnicki.
I'm curious, would running the Flatpak version of Steam "fix" this by providing its own glibc?
You know, for the people that want to stay on an old glibc yet are also comfortable with using Flatpak.
Yes, but which OS is still running glibc < 2.31?
Almost Linux Mint Debian (2.32)
Debian Trixie 2.41-7 Debian stable 2.36-9
I think they are preparing their next edition soon.
It should.
I use Arch (btw) so I'm not worried about it