Quoting: Vortex_AcheronticNative Linux version seem to no longer work

What's the issue?

I had problems in the past getting F1 2017 to run after I upgraded to Ubuntu 22.04. It seemed to rely on functions from glibc that were marked private and have been removed with version 2.34. I found a solution that brings back the functions in question: https://github.com/vkc-1974/XCOM2WotC-f35. Give it a try, maybe it'll work in your case as well.

Quoting: GuestLinux will get there but didn't have the industrial planning Windows did

There are actually quite a lot of old Software no longer functional on modern versions of Windows. While the same software often times runs fine using Wine on Linux. At least this is my subjective experience since I started using Linux around 2005.

What I call industrial planning though are flatpak and snapcraft runtimes. Which ensure an app or game developed for a specific runtime will keep working even on the most recent system 10 or more years later as it still can make use of the same runtime and thus libraries.

As of why DiRT does no longer works: Well there quite a few reasons but is all boils down to Feral Interactive doing weird hacky things they shouldn't have done in the first place and shipping Ubuntu 16.04 32bit libraries with their game. Again something they should never had to do even back then. Dunno why they did though.

But Feral Interactive Ports, at least their old ones, are famous of not working quite right on anything which is not closely related to the version of Ubuntu they ported the game on.

Two counter examples of native Linux games still working today are: the 1999 Unreal Gold (even without community patches) and Fitzquake SDL

Quoting: kaimanWhat's the issue?

There are two for which I did not yet found a sophisticated solution. Surprisingly even the "usual fixes" I am used to do with Feral ports do no longer work.

1st: They try to discover libraries on their own which fails. But I managed to fix it by overwriting LD_LIBRARY_PATH but this led to the next issue.

2nd: They ship an ancient 32bit version of SDL 2.0.5 which then causes a segmentation fault. Even with the Steam runtime which is based off Ubuntu.

However simply removing their bundled SDL libraries does not solve the issue as it will then no longer find it at all. Not evne the SDL provided by the system or the Steam Runtime. Maybe because of the weird way they try to discover libraries on their own? Dunno.

Last edited by Vortex_Acherontic on 7 April 2024 at 10:17 pm UTC

Quoting: GuestThe beauty of Linux is you can install Ubuntu 16.04 if you want to any time

I don't think it will even post on my hardware. Running it inside a VM wouldn't be a great gaming experience I suppose.

Also running EOL operating systems, no matter if it is windows or Linux isn't a very good idea either.

Quoting: Vortex_AcheronticThere are two for which I did not yet found a sophisticated solution. Surprisingly even the "usual fixes" I am used to do with Feral ports do no longer work.

Too bad, but this really seems a completely different beast. F1 2017 is already 64bit, which simplifies things a lot, I guess.

If the segfault happens within SDL, there might at least be a chance to figure out what the cause for that is, and try to fix it, but it likely would need a lot of work and an old 32bit system to compile a suitable replacement. Unless the version they ship with the game has been heavily customized ...

Quoting: kaiman

Quoting: Vortex_AcheronticThere are two for which I did not yet found a sophisticated solution. Surprisingly even the "usual fixes" I am used to do with Feral ports do no longer work.

Too bad, but this really seems a completely different beast. F1 2017 is already 64bit, which simplifies things a lot, I guess.

If the segfault happens within SDL, there might at least be a chance to figure out what the cause for that is, and try to fix it, but it likely would need a lot of work and an old 32bit system to compile a suitable replacement. Unless the version they ship with the game has been heavily customized ...

They have backported a few things from elsewhere yes. But in all honesty I rather just boot up the game using Proton instead of fixing weird Linux ports 😅

Launches out of the box for me on Mint 21.3 and runs fine, for what it's worth. I can only test at 1080p, but the bench gave me 90 min / 124 avg / 192 max FPS at Ultra / 8x MSAA on my slightly older system (check my PC info for details). I suppose I'll have to test if it stops working after the next major Mint update.

You should always try forcing one of the Steam Linux Runtime versions before doing any manual library trickery, that's often enough to get older games running.

Quoting: tuubiLaunches out of the box for me on Mint 21.3 and runs fine, for what it's worth. I can only test at 1080p, but the bench gave me 90 min / 124 avg / 192 max FPS at Ultra / 8x MSAA on my slightly older system (check my PC info for details). I suppose I'll have to test if it stops working after the next major Mint update.

You should always try forcing one of the Steam Linux Runtime versions before doing any manual library trickery, that's often enough to get older games running.

I did try the Steam Linux runtimes before manually trying to fix it. They do not work either. 😕

Last edited by Vortex_Acherontic on 8 April 2024 at 8:18 pm UTC

Native Linux version is indeed still working...
Kubuntu 23.10 Nvidia RTX 4070
dpkg --add-architecture i386 for 32bit libraries needed by steam, 32bit libraries for proprietary drivers installed,

fires right up for me...

Quoting: iwantlinuxgamesNative Linux version is indeed still working...
Kubuntu 23.10 Nvidia RTX 4070
dpkg --add-architecture i386 for 32bit libraries needed by steam, 32bit libraries for proprietary drivers installed,

fires right up for me...

As I suspected it only runs reliably on Ubuntu (as of now). Which doesn’t solve the issue that weird hacky things where done in order for the game to even boot up and it apparently does not work well. Especially since I run it from flatpak steam whos runtimes are based of Ubuntu 23.04 btw. Even after forcing the the Linux Runtime 1.0 (scout) which is based off Ubuntu as well the game does not work.

The actual error is:

=== ERROR - You're missing vital libraries to run DiRT Rally
=== Either use the steam runtime or install these using your package manager
ERROR: ld.so: object '/home/vortexacherontic/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
/home/vortexacherontic/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/DiRT Rally/bin/DirtRally: /home/vortexacherontic/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_64/libcurl.so.4: version `CURL_OPENSSL_4' not found (required by /home/vortexacherontic/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/DiRT Rally/bin/DirtRally)

Funny enough it is lib curl in version 4 it has located and still it refuses to work with it. In fact it is even Ubuntu’s custom libcurl-gnutls.so.4 not to be found on any other Linux distribution but Debian and Ubuntu.

Also:

QuoteEither use the steam runtime

It already uses the Steam runtime ...

Followed by:

/home/vortexacherontic/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/DiRT Rally/bin/DirtRally: error while loading shared libraries: libSDL2-2.0.5.so: cannot open shared object file: No such file or directory
'DiRT Rally' quit with error code '127'.

Which is funny too because it is not finding the library the game ships on it's own.

After lengthy LD overwrites such as:

LD_LIBRARY_PATH=/home/vortexacherontic/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/DiRT\ Rally/lib/x86_64:/home/vortexacherontic/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu/:/home/vortexacherontic/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu/ %command%
The game then finds all libraries, because they are all there, but then just core dumps...

Anyway it shouldn't be the responsibility of the user to fix broken Linux ports which just happen to work for some.
So Proton it is.

As a side note, not all Feral Ports are broken though.

XCOM 2 (Linux release: Feb 5. 2016) -> broken
XCOM 2: War of the Chosen (Linux release: Dec. 3rd 2018) -> Works with no modifications. This one even is just a DLC
Rise of the Tomb Raider (Linux release; April 19, 2018) -> Works with no modifications
Shadow of the Tomb Raider (Linux release: November 5, 2019) -> Works with no modifications
Tomb Raider (Linux release: April 27, 2016) -> broken
Deus Ex: Mankind Divided (Linux release: November 3, 2016) -> broken
Middle-Earth: Shadow of Mordor (Linux release: July 30, 2015) -> broken
DiRT Rally (Linux release: March 2, 2017) -> broken

Looking at the release dates it seems in older Linux ports Feral did some things apparently the wrong way. Which they fixed around 2018 it seems. But then stopped doing Linux ports in 2020ish as they finally got thing in order ... *sad noises*

Edit: I just tested a few other Feral Ports and interestingly the old Dawn of War II port still works. The Linux version was released on September 29, 2016 while DiRT was one year later and does not work. 🧐

Last edited by Vortex_Acherontic on 10 April 2024 at 11:43 am UTC