You can sign up to get a daily email of our articles, see the Mailing List page!
Support me on Patreon to keep GamingOnLinux alive. Funding me on Patreon allows us to have no adverts, no paywalls, no timed articles. Just good content for you to keep up with Linux gaming. Alternatively, you can support me on Paypal.

It seems an update of glibc has caused a bunch of Linux ports from Feral Interactive to be broken. Here's a possible workaround for now.

Add this as a launch option:

LD_LIBRARY_PATH="/path/to/steam/games/steamapps/common/gamename/lib/x86_64/" %command%Set it to the correct install path and replace "gamename" with the name of the game.

That can be placed by right clicking the game in Steam, going to Properties, hit Set Launch Options and put that in.

While stuff like this doesn't happen too often, it is one of the problems of being on a rolling distribution. Updates can break stuff! It's why even after I posted about how I loved Antergos, I'm back and happy on Ubuntu on my main gaming machine, so I don't have to deal with stuff like this.

I've emailed the PR people at Feral Interactive to let them know, and to see if we can get a comment on what they plan to do. It's worth noting the bug was reported to them nearly a month ago and so they should already be aware.

Hopefully this will be sorted before too long. Feral will need to sort it, since Ubuntu and others will update before too long. It could be a regression in the updated packages and not intentional to be fair, so it might not be Feral's problem to solve.

8 Likes, Who?
Comments
Page: «6/6
  Go to:

N30N 14 September 2017 at 3:42 am UTC
STiATI've looked a bit closer at this, and it seems that Feral / games with this issue use glibcs hwcaps to determine the architecture. Formerly, it reported x86_64 on all x86_64 platforms, and seems to have moved on to reporting either haswell or xeon_phi (side-note, for x86 it reported i386, i486, i586, i686, so managing different x86_64 platforms actually makes sense on a long-run).

Not sure if we can lay that out as ABI break, but it seems very much like it, since it used to report something different from 2.25 to 2.26.

Fact is, I'm a not so sure if it's wise to rely on hwcaps for determining the target platform, or in other words, rely on it to determine the path for your platform specific libraries.

It should be pretty easy to fix for Feral if they want to, but they'd have to do that for all their games...

But doing getconf LONG_BIT or uname -m seems more reliable than going for glibcs hwcaps which can be subject to change on new architectures.
See $LIB under the Rpath token expansion section of man ld.so.
Dolus 14 September 2017 at 4:54 am UTC
Could shipping games themselves in Flatpak/Snap format mitigate this library breakage problem? From a practical standpoint, this would be a major turn-off to would be former Windows users who are used to their games running for 10+ years.
lucinos 14 September 2017 at 6:57 am UTC
DolusCould shipping games themselves in Flatpak/Snap format mitigate this library breakage problem? From a practical standpoint, this would be a major turn-off to would be former Windows users who are used to their games running for 10+ years.

flatpak is a step to the right direction but is not a complete solution yet. (snap - first I do not trust at all canonical as they are very responsible for the mess in the first place)

Windows is also a mess but they have been the major platform for many years so it is better. I do not doubt linux will be there in 10 years but I am quite angry and disappointing because we had a chance to do things right from the very beginning (that was 2012) but Valve and Canonical blundered miserably. If things were done right from the start this could actually be a great advantage of Linux against windows.
jaycee 14 September 2017 at 9:09 am UTC
"Windows is also a mess" but it solved this problem ages ago with app manifests and SxS. Also ABI breakage generally does not happen on Windows to the extent it does on Linux... there's no single points of failure like glibc for example.

Flatpak isn't really a good solution. It's just basically shoving a huge tree of libraries into a folder and then making sure the app uses everything in that. For smaller deps like SDL, openal-soft, freetype etc that is far better done by the developer themselves. Bundling major system components like pulse/alsa/x11 libs/mesa/glibc just leads to nasty breakage or security issues.
Dolus 14 September 2017 at 7:07 pm UTC
jayceeFlatpak isn't really a good solution. It's just basically shoving a huge tree of libraries into a folder and then making sure the app uses everything in that.

Sounds more like AppImage... I thought multiple flatpaks could all run on the same runtime, mitigating the amount of libs you'd have to bundle with each flatpak?
mirv 14 September 2017 at 7:25 pm UTC
View PC info
  • Supporter
Dolus
jayceeFlatpak isn't really a good solution. It's just basically shoving a huge tree of libraries into a folder and then making sure the app uses everything in that.

Sounds more like AppImage... I thought multiple flatpaks could all run on the same runtime, mitigating the amount of libs you'd have to bundle with each flatpak?

Multiple programs all running of the same runtime....almost like it's a system for running the programs, or for operating them....we should call it an operating system!

Jokes aside, going down that route has exactly the same problems in the end. I don't think flatpaks are the answer here either.
Dolus 14 September 2017 at 7:43 pm UTC
mirvJokes aside, going down that route has exactly the same problems in the end. I don't think flatpaks are the answer here either.

I think Flatpak is part of the solution. But we have to do something about glibc ABI breakage to really solve the problem.
  Go to:
While you're here, please consider supporting GamingOnLinux on Patreon. We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!

We also accept Paypal donations! If you already are, thank you!

Due to spam you need to Register and Login to comment.


Or login with...

Popular this week
View by Category
Contact
Latest Forum Posts
Facebook