It seems an Arch update today has broken a few games, several Feral Interactive titles as well as Civilization VI from Aspyr Media no longer run.
It's apparently an issue with the Arch update of openssl. I sadly updated without knowing it was an issue, so certain games are now broken for me. I've had this confirmed by multiple other reports, so it's certainly not me. There's also a bug report open for it.
Titles I've personally tested that no longer load:
Here's an example of what happens when XCOM 2 won't launch now:
This is just a PSA to highlight the issue. Feel free to share any helpful tips in the comments.
Plenty of games do still work though, it does not affect all games.
Update: A workaround is to install libopenssl-1.0-compat and use that for the games that don't work.
You can then add this to the launch options of the games that don't work:
Another workaround is to re-install an earlier version by doing:
Downgrading isn't always advisable, I tested both methods and both work. Installing the AUR package is probably the better solution.
It's apparently an issue with the Arch update of openssl. I sadly updated without knowing it was an issue, so certain games are now broken for me. I've had this confirmed by multiple other reports, so it's certainly not me. There's also a bug report open for it.
Titles I've personally tested that no longer load:
- DiRT Rally
- HITMAN
- Dawn of War II
- XCOM 2
- Civilization VI
- Probably others too
Here's an example of what happens when XCOM 2 won't launch now:
Quote/mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/XCOM2: /usr/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/XCOM2)
/mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/XCOM2: /usr/lib/libldap_r-2.4.so.2: no version information available (required by /mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/../lib/x86_64/libcurl.so.4)
/mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/XCOM2: /usr/lib/liblber-2.4.so.2: no version information available (required by /mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/../lib/x86_64/libcurl.so.4)
/mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/XCOM2: /usr/lib/libssl.so.1.0.0: version `OPENSSL_1.0.1' not found (required by /mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/../lib/x86_64/libcurl.so.4)
/mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/XCOM2: /usr/lib/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/../lib/x86_64/libcurl.so.4)
/mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/XCOM2: /usr/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /mnt/storage/SteamLibrary/steamapps/common/XCOM 2/bin/../lib/x86_64/libcurl.so.4)
This is just a PSA to highlight the issue. Feel free to share any helpful tips in the comments.
Plenty of games do still work though, it does not affect all games.
Update: A workaround is to install libopenssl-1.0-compat and use that for the games that don't work.
You can then add this to the launch options of the games that don't work:
LD_LIBRARY_PATH=/usr/lib/openssl-1.0-compat/ %command%
Another workaround is to re-install an earlier version by doing:
pacman -U https://archive.archlinux.org/packages/o/openssl-1.0/openssl-1.0-1.0.2.k-2-x86_64.pkg.tar.xz
Downgrading isn't always advisable, I tested both methods and both work. Installing the AUR package is probably the better solution.
Some you may have missed, popular articles from the last month:
Maybe we should standardize gaming to chroot/LXC/docker with a specific distro. I like my main distro to be secure, and in between stable and bleeding edge, but for gaming I don't really care as long as it works. I will for sure not do any symlinking override systemwide. If I want symlink override I rather do it on a per game basis and use shellscript for launch if needed.
2 Likes, Who?
looks like there's a bit more broken than just openssl, the update for GNOME to 3.24 dropped as well which apparently there are a number of extensions are broken beyond just updating the metadata.json.
Downgrading will break pacman and other parts that depend on the newer version. symlinking is about the only temp fix. but I don't like doing that and it's typically a bad idea.
Looks like I'll be distro hopping for a bit until this is sorted out.
Downgrading will break pacman and other parts that depend on the newer version. symlinking is about the only temp fix. but I don't like doing that and it's typically a bad idea.
Looks like I'll be distro hopping for a bit until this is sorted out.
0 Likes
Quoting: neowiz73looks like there's a bit more broken than just openssl, the update for GNOME to 3.24 dropped as well which apparently there are a number of extensions are broken beyond just updating the metadata.json.
Downgrading will break pacman and other parts that depend on the newer version. symlinking is about the only temp fix. but I don't like doing that and it's typically a bad idea.
Looks like I'll be distro hopping for a bit until this is sorted out.
That not what I want to hear. I just switched to gnome from KDE. Do you know what extensions are broken? I have held off updating my arch. I don't really want to roll a new distro, but I don't want to hvae to deal with these issues either.
0 Likes
Quoting: m0nt3Quoting: neowiz73looks like there's a bit more broken than just openssl, the update for GNOME to 3.24 dropped as well which apparently there are a number of extensions are broken beyond just updating the metadata.json.
Downgrading will break pacman and other parts that depend on the newer version. symlinking is about the only temp fix. but I don't like doing that and it's typically a bad idea.
Looks like I'll be distro hopping for a bit until this is sorted out.
That not what I want to hear. I just switched to gnome from KDE. Do you know what extensions are broken? I have held off updating my arch. I don't really want to roll a new distro, but I don't want to hvae to deal with these issues either.
so far twitchlive_panel, caffeine and openweather. but overall the openssl was what really killed it for me.
0 Likes
Well, I update every week for reasons such as this. However, if it still breaks my system without that upgrade, I have three other USB sticks to go through.
0 Likes
Hopefully it gets resolved before I run my next routine updates. (I don't update every day.) I'll check the status of this problem before I do so! Thanks for the heads-up.
Switch to a different distro over this? Ha! Haaaahahahahaahahahahaahahahahahahahahaahahahaaaaaaaa
Switch to a different distro over this? Ha! Haaaahahahahaahahahahaahahahahahahahahaahahahaaaaaaaa
3 Likes, Who?
Quoting: STiAT<caugh>..openssl-1.0 is not enough because it just installs libssl.so etc in /usr/lib/openssl-1.0/. So if a game link to libssl.so.1.0.0 (most of the case) it won't work, and if it links to libssl.so, you still need to use LD_LIBRARY_PATH=/usr/lib/openssl-1.0
sudo pacman -Sy openssl-1.0
0 Likes
I havent played any games since the update. But it did a number on Spotify also. Looking through the comments on AUR I had to install some compat packages and update Spotify and it was working again.
Arch can be a blessing and a curse. I like it for getting the latest performance and dev on my GPU tho.
Last edited by lejimster on 27 April 2017 at 10:22 am UTC
Arch can be a blessing and a curse. I like it for getting the latest performance and dev on my GPU tho.
Last edited by lejimster on 27 April 2017 at 10:22 am UTC
0 Likes
Looking at bug 53618 seems priority is still marked as low and no resolution as of yet.
Don't really want to bother with work arounds.
Will hold off on upgrading for now.
Only felt the blessing so far , seems I was due for the curse. :(
Don't really want to bother with work arounds.
Will hold off on upgrading for now.
Quoting: lejimsterArch can be a blessing and a curse.
Only felt the blessing so far , seems I was due for the curse. :(
0 Likes
As much as I love Arch, I am thinking I may have to jump over to one of the *buntus.
0 Likes
See more from me