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.
Quoting: GuestThe problem is that the people who could do something about this, dont want to. They see it as a problem only affecting closed source software, and thus not worthy of any attention.
Lately, they actually have been fixing bugs that only breaks closed source software. In fact, there was a change that broke older 64-bit Unity games in Arch, and that got fixed.
Quoting: GuestQuoting: DolusThe glibc bug I'm referring to:
https://bugzilla.redhat.com/show_bug.cgi?id=1440287
Notice the first comment from one of the maintainers.
Not seeing the problem. Sure, the reply assumed you'd be able to recompile whatever was broken, but the bug got fixed.
Quoting: BrisseFeral games stopped working for me on Ubuntu 17.10 a few days ago. Remembered this article and suspected the issue might be related, however, the workaround provided does not work for me. Anyone else with Ubuntu 17.10 who have run into issues lately?
Yep, me.
Quoting: AnjuneYep, me.
I was in contact with someone at Feral and they were kind enough to report the bug to Canonical, and apparently it's been fixed upstream, but that fix has yet to make it's way into Ubuntu. Should only be a matter of time though.
Basically,
cd
to the game's lib
directory and run ln -s x86_64/* .
-- worked with Life is Strange and Shadow of Mordor, haven't tried any others yet.Edit: Tried on Ubuntu 17.10
Last edited by Anjune on 28 September 2017 at 8:47 pm UTC
Quoting: AnjuneI found a workaround that works here: https://www.reddit.com/r/linux_gaming/comments/70k7t9/mad_max_wont_run_on_slackwarecurrent_steam/
Basically,cd
to the game'slib
directory and runln -s x86_64 .
-- worked with Life is Strange and Shadow of Mordor, haven't tried any others yet.
Edit: Tried on Ubuntu 17.10
Thanks! Worked for all my currently installed Feral games, including Dirt Rally which I recently bought and haven't played yet so that makes me really excited :)
Oh, and the last line should be
$ ln -s x86_64/* .
Didn't work without the asterix for me.
Last edited by Brisse on 28 September 2017 at 8:41 pm UTC
See more from me