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. This ensures we have no timed articles and no paywalls. Just good, fresh content! We will also never show adverts to anyone who supports GamingOnLinux! 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: «2/8»
  Go to:

stan 11 September 2017 at 1:08 pm UTC
GnurfosSteam provides a "runtime" (a bunch of libs, not in the games folders). Shouldn't games be using that, and not be impacted by system updates ?
That’s the idea, but in reality games use a mix of:
- their own libs
- the steam runtime
- the system libs

The Steam runtime just adds more complexity to the problem and often breaks games because it provides libs that should be system-only (libstdc++ or pulseaudio for example). Moreover Valve added a new mecanism a while ago to prefer using the system libs instead of the runtime libs so it’s even more complicated now. This new mecanism made some games work for some people and broke other games for other people (me).
cprn 11 September 2017 at 1:25 pm UTC
Do you not run Steam runtime anyway? I see no point in running native libs that might or might not work with a particular title. It's way more effective to just use what's provided and tested.


Last edited by cprn at 11 September 2017 at 1:28 pm UTC. Edited 2 times.
Ray54 11 September 2017 at 2:02 pm UTC
View PC info
  • Supporter
I am pleased that you are back on Ubuntu (I assume 16.04) for your main machine. I want to be able to read your game reviews and assume that I will get similar playability and reliability on my 3 older Linux Mint 18 gaming desktops. I have nothing against other Linux distributions, but as I said when you first moved to Antergos, I did not feel that it reviews using Antergos would be as useful as reviews using Ubuntu to the majority of your readership.
BTRE 11 September 2017 at 3:02 pm UTC
  • Contributing Editor
  • Supporter
Ray54I am pleased that you are back on Ubuntu (I assume 16.04) for your main machine. I want to be able to read your game reviews and assume that I will get similar playability and reliability on my 3 older Linux Mint 18 gaming desktops. I have nothing against other Linux distributions, but as I said when you first moved to Antergos, I did not feel that it reviews using Antergos would be as useful as reviews using Ubuntu to the majority of your readership.
According to GOL's own statistics, Ubuntu users are the largest single group but definitely not the majority of users. So it's actually more useful to the majority to know how it runs on non-Ubuntu distros using your logic. Still, in practice, it doesn't really matter what distro we're on since it's rare for there to be really significant issues with games. At least something that won't eventually affect all distros, as is the case with this glibc thing.
sbolokanov 11 September 2017 at 4:29 pm UTC
GnurfosThere's something I don't understand, can someone clarify :
  • In addition, why would there be libs already present in a game's folder, which are not used by default by the game launcher ?
The problem is that it can't find thouse game libs. That's the whole problem.
Samsai 11 September 2017 at 4:40 pm UTC
cprnDo you not run Steam runtime anyway? I see no point in running native libs that might or might not work with a particular title. It's way more effective to just use what's provided and tested.
Steam runtime is not exactly a perfect solution either. It worked decently well for a while until libstdc++.so along with some other libraries in the runtime became so outdated they broke OpenGL support on open source drivers. That forced a lot of people to abandon the runtime in favour of Steam native. Then Valve went and kind of fixed the problem by preferring host libraries, with the result that stuff is broken now because now a system library gets loaded and is incompatible with the game.

I don't think there's a single winning move with the current setup. Steam runtime is in a serious need of updates and central libraries in general should put more effort into backwards binary compatibility.
Duckeenie 11 September 2017 at 4:42 pm UTC
Will be very interesting to monitor their response to this. It would put me right off paying full price for games if I thought their lifespan was severely limited. Feral Interactive seem like a good bunch though so hopefully things turn out well.
property 11 September 2017 at 4:55 pm UTC
Ubuntu 16.04 is also affected when upgrading Mesa. XCOM 2 WotC keeps crashing after I've installed Mesa 17.2. After reinstalling the Mesa 17.0.7 it just fine.

However, Warhammer DoW 3 seemed to be working with Mesa 17.2 as well as 17.3-git
liamdawe 11 September 2017 at 5:04 pm UTC
propertyUbuntu 16.04 is also affected when upgrading Mesa. XCOM 2 WotC keeps crashing after I've installed Mesa 17.2. After reinstalling the Mesa 17.0.7 it just fine.

However, Warhammer DoW 3 seemed to be working with Mesa 17.2 as well as 17.3-git
Different issue, contact Feral support and log the issue on the Mesa bug list.
stan 11 September 2017 at 5:08 pm UTC
DuckeenieIt would put me right off paying full price for games if I thought their lifespan was severely limited.
That’s why I’m not buying anything on Steam anymore. Too many ways for the games to stop working and it’s impossible to prevent the automatic game and runtime updates. If you buy a game and it doesn’t work then you can get a no-questions-asked refund and that’s great, but if it stops working one year later because of a runtime update, like Tropico 5 just did for me, you’re just screwed.
  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...

Livestreams & Videos
Community Livestreams
See more!
Popular this week
View by Category
Contact
Latest Forum Posts
Facebook