Libcurl issue with openssl 1.1 [Tumbleweed][Arch]

[moozaad]

I've raised this before on reddit but thought I'd better document it better.

Xcom and Madmax fail on opensuse tumbleweed due to steam runtime issues. I have no idea why you're including a copy of libcurl when it's a very common system library with a stable ABI.

For reference:
https://abi-laboratory.pro/tracker/timeline/curl/ - ABI stability
https://repology.org/metapackage/curl/information - ABI availability

Our work around is simply Mad Max/lib/x86_64> mv libcurl.so.4 libcurl.so.4_

My suggested fix is not to include libcurl, but instead install it as necessary from the distro.

[mdiluz]

Thanks for the report @moozaad. We've been aware of this for some time. From what I know it should be resolved in newer games (released after May 2017) - we've swapped to libressl instead of openssl which works around the problem for now. Dawn Of War 3 for example should already have the change so if you still hit the same issue with there then let us know.

We appreciate noting the workaround, that should help any other users who come into contact with this issue while we work towards patching older games.

This problem came from linking our libcurl directly with the steam runtime version of libssl, calling itself libssl.1.0.0 but having OPENSSL_1.0.1 available. When steam swapped to preferring native libraries in this update it broke compatibility for us, as the SUSE (and other distro) versions of libssl.1.0.0 don't provide OPENSSL_1.0.1 .

We'd certainly prefer to use the system libcurl, but due to a few complications with the steam runtime we currently can't. Those should be resolved in due course.

[moozaad]

Yeh, 1.0.2 and 1.1 here. That solution is probably for the best. Is there an ETA for the older games' launchers to be moved to libressl?

[mdiluz]

I don't have any specifics I'm afraid. We'll be patching in roughly priority order though based on the amount of user feedback, so I'll add yours to our pool.

If I get a chance I'll update this comment with a set list of games that need this fix and haven't received it already. That'll help users know when this workaround is needed.

[moozaad]

This issue is still present with madmax after the latest patch.

[dotWAVE]

I bought DiRT Rally today and had the same issue.

[mdiluz]

@moozaad and @dotWAVE, unfortunately both of those games do not have this fix yet, they're on our list though

[mdiluz]

Also worth noting that the steam-native-runtime package on Arch now depends on openssl-1.0 and so works around this issue for us in testing. So if you find yourself on this bug report as an Arch user you may want to install steam-native-runtime first and see if that fixes your issue.

[moozaad]

Warhammer still has the issue and that was updated just yesterday!

[mdiluz]

@moozaad Yup, that's correct. We have the fix for Total War Warhammer still in production, unfortunately. I'll adjust the original post so it's less misleading.

[mdiluz]

I expect this issue will begin to affect Ubuntu with 17.10 (releasing Oct 19th).

We're working to back-port patches to all old games affected, but for now extracting this zip into the lib/x86_64 directory in the game install path can work around the issue locally.

It's a steam runtime and system compatible versions of libressl, crypto and curl.

lib-x86_64-override.zip

[moozaad]

Can confirm that it does work with TWWH on tumbleweed. Is it it being backported to the whole library?