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

Linux Gaming

18042 readers
691 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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 72 points 1 day ago (1 children)

2.31 was released on 2020-02-01.

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

That's surprisingly new. Wonder what causes the incompatibility

[–] [email protected] 41 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] 38 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.