[2.1.7] Game does not start in steam on linux

[Rokis]

After updating the game it does not start.
Steam shows game running for a brief moment and it closes.
Game window does not appear, log doesn't record anything.
Restarting the pc and steam did not help

[Amarula]

Did you uninstall the old version? apparently this is required...

[berggen]

+1

viewtopic.php?t=134100

If you're running an old version of Linux you may need to upgrade (I'm on Ubuntu 22.04 and looks like I need to upgrade to 24.04).

I think this should be considered a bug and not moved to tech help though.

[Prommah]

Assuming this is the same problem as in berggen's thread, this is not just an issue with Steam as was suggested there. If this is the same glibc issue, it occurs with the standalone Linux client as well.

[raiguard]

Please ensure you are on the latest version of your linux distribution. We upgraded the glibc requirement in 2.1.

[Merssedes]

Please ensure you are on the latest version of your linux distribution. We upgraded the glibc requirement in 2.1.

No mention of this in changelog?

[Rokis]

There kind of is: "Updated to SDL 3.". But for me it doesn't mean anything. I feel like it should have been mentioned in the last FFF, before the update dropped.

P.S. I updated my system to mint 22 and game launched without any problems

[raiguard]

SDL 3 didn't directly require an updated glibc, but what it did cause was us needing to update the build process to use Debian 12 so we can get access to more updated versions of Wayland and Pipewire which Debian 11 does not ship with. You are right that we neglected to mention this in the changelog.

There are a few potential solutions we are looking into to try and lower the glibc requirement again. Stay tuned.

[raiguard]

We have updated the experimental branch on steam to use Steam Linux Runtime 4.0, which ships with a newer glibc. Please check if this fixes the problem for you. We will keep looking into ways to lower the glibc requirement for the standalone version.

[Prommah]

We have updated the experimental branch on steam to use Steam Linux Runtime 4.0, which ships with a newer glibc. Please check if this fixes the problem for you. We will keep looking into ways to lower the glibc requirement for the standalone version.

Can confirm it fixes it. After undoing Daniel0x00's fix so that I'm just running it normally without any configuration, both 2.1.7 and 2.1.8 now launch perfectly fine through Steam. Thanks!