While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations:
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Bazzite Linux gets a spring cleaning update to end 2025
- Valve reveal the most popular Steam games of 2025
- Native Linux support for Hytale will be launched as "experimental"
- Steam survey for December 2025 shows Linux holding to 3.19% [updated]
- D7VK v1.1 is out with experimental Direct3D 6 support via Vulkan for Windows games on Linux
- > See more over 30 days here
- Welcome back to the GamingOnLinux Forum
- Xpander - Will you buy the new Steam Machine?
- Jarmer - 2026 Gaming Goals...?
- Klaas - Will you buy the new Steam Frame?
- Klaas - Introduce Yourself!
- Mustache Gamer - See more posts
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
View PC info
when I try to launch Metro Exodus I get an error message telling me that my libc version is too old for the game to run (Is: 2.27 - should be: >2.29). With libc being an integral component of linux I can't just force upgrade to a newer version, unless I really want to completely trash my system.
Since I'm very happy with my current setup I'm not planning to upgrade to a newer linux until mid next year, and if I can't get the game to run with this version, well, then it'll sit idle in my library for a bit, not a big deal.
I'm still trying to figure out if it's possible, either with a localized install of libc >2.29 exclusively for Metro to use, or, if possible, just fool the game into assuming that I have the correct version installed, since I don't think Metro actually needs this version to run and it just checks because the binary was built with it.
Not sure if any of this is actually possible, but if anyone has an idea, appreciated :happy:
You can try my self-compiled library of GLIBC 2.29 (don't delete the other files in the folder, you might need them too) - https://drive.google.com/file/d/1o1kOPiVazvNxKQ6jaRBc3bVhrxjLhCO2
Try passing the - LD_PRELOAD="/path/to/libc-2.29.so" to force the game to use that instead of the default system one.
If you still get stuck please post the terminal log here :grin:
View PC info
Lately a similar error occurred in Surviving Mars, with the new update, because people at Paradox used a newer compiler and now it won't work on "old systems", even if they are among the officially supported ones. But this is entirely their fault and hopefully they fix it soon. Your case is most likely not an accident, but deliberate.
damarrin: Win10 is a wrong example, as it is continuously updated with new "packages". If it cannot do that, then some programs already complain that "your Win10 version is too old". So we actually have multiple Win10 operating systems (quite a few at that), not simply a 6 year old one.
Last edited by tuxintuxedo on 18 Apr 2021 at 3:44 pm UTC
I found the following thread: https://steamcommunity.com/app/464920/discussions/0/3168820451548416725/
Seems like another case of GLIBC. I'll look into it for those that have the issue.
EDIT: Yep, confirmed giving GLIBC error.
EDIT 2: Got it running too.
In case anyone is running into the issue and wants to give it a shot, download the package I uploaded above for the OP. Run the game with LD_PRELOAD="/path/to/libm.so.6" (as shown in screenshot).
Last edited by Avehicle7887 on 18 Apr 2021 at 6:25 pm UTC
View PC info
Case closed, thanks a lot! :happy:
They even used year and month number versioning until recently, with 1909, 2004 (released in May 2020 though) but now its changed to 20H2 and the next will be called 21H1 https://en.wikipedia.org/wiki/Windows_10_version_history
There have been some problems, but checking on those showed that it either was due to stupid misconfigurations on my part, or PPAs that I have added. And I always was able to get through the upgrade once I found the problem.
It has been years since I ran into any problem due to release upgrades, its about keeping a well maintained system, and knowing which PPAs can cause problems.
Use ppa-purge on the problematic PPAs, or just any if in doubt. This will uninstall packages from the PPA and where available install the versions from the Ubuntu repositories.
........../SteamLibrary/steamapps/common/SteamLinuxRuntime_soldier/run-in-soldier %command%