this post was submitted on 22 Apr 2025
200 points (100.0% liked)

Linux Gaming

18008 readers
909 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
 

To check which version of glibc you have, run ldd --version in the terminal.

top 34 comments
sorted by: hot top controversial new old
[–] [email protected] 5 points 14 hours ago

I use Arch (btw) so I'm not worried about it

[–] [email protected] 21 points 21 hours ago* (last edited 20 hours ago) (2 children)

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.

[–] [email protected] 16 points 20 hours ago (1 children)

Yes, but which OS is still running glibc < 2.31?

[–] [email protected] 8 points 18 hours ago (1 children)

Almost Linux Mint Debian (2.32)

[–] [email protected] 2 points 16 hours ago (1 children)

Debian Trixie 2.41-7 Debian stable 2.36-9

[–] [email protected] 1 points 12 hours ago

I think they are preparing their next edition soon.

[–] [email protected] 9 points 21 hours ago
[–] [email protected] 100 points 1 day ago

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.

[–] [email protected] 70 points 1 day ago (1 children)

2.31 was released on 2020-02-01.

[–] [email protected] 38 points 1 day ago (1 children)

That's surprisingly new. Wonder what causes the incompatibility

[–] [email protected] 40 points 1 day ago* (last edited 1 day ago) (1 children)

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.

[–] [email protected] 37 points 1 day ago

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.