Issues for enabling Steam games to run with the Solus runtime.
Jan 7 2021
I think installing the hidapi package fixed the issue for me, though I also installed the xboxdrv and hidapi-32bit packages too for good measure.
Dec 30 2020
I am able to reproduce this using an 8bitdo SN30 Pro+ controller in xinput mode (emulates an xbox one controller). With "Use the intercept library" enabled, Steam does not recognize the controller (though I too can get input in other applications such as sc-controller), while with the option disabled Steam recognizes the controller as an xbox one controller. However, if I put the controller in switch-mode (emulates a nintendo switch controller), I do get Steam to recognize the controller with "Use the intercept library" enabled.
Dec 14 2020
Dec 9 2020
Nov 27 2020
Oct 30 2020
Yes I did close it completely and then made the changes. It is still not working, however flatpak version is there now. Want to have it working without flatpak. Please do let ne know if there is anything that can be done to fix it
Oct 12 2020
I tried disabling it and I still have no luck,
I tried steam on flatpak, and the game launches fine there, No issues observed.. I can use it with Flatpak for some time, however I am 100% sure that the performance is not as good as it would be without Flatpak.
Oct 11 2020
I tried disabling it and I still have no luck, I also disabled the Unity Games Workaround too., I do not have success. I get the below error.
: error while loading shared libraries: /usr/lib/libcrypto.so.1.0.0: wrong ELF class: ELFCLASS64
@osgyan I take it you have already tried different settings in "Linux Steam Integration"?
I am also unable to launch Borderlands 2. all other games work absolutely perfection. Any ideas on what could be the issue?
Jun 4 2020
It seems to be working fine now (with native runtime and intercept library set to ON).
May 28 2020
Is this still an issue?
May 5 2020
Feb 5 2020
Dec 18 2019
So it's possibly the 32bit libsdl2 exemption causing the issue (which would need a new LSI to test), or requires incompatible bundled libs and needs to be exempted from libintercept.
Dec 13 2019
Yes, it works with native runtime (ON) and the intercept library (OFF).
Does it work in this configuration?
Dec 11 2019
Dec 3 2019
It didn't seem to make any difference, at least for me. I also tried to force the CFLAGS to just "-O2" and then "-O0", but it made no difference.
Lastly I tried building alsa-lib with clang and there seems to be no difference in starting Borderlands 2.
I honestly don't know if I am doing something wrong here (don't know how to run the backtraces for example)...
Good idea! @aleksvor. I will give it a shot today or tomorrow if I get some time over 👍
It's a blind guess, but I think we can try building alsa-lib without tree-vectorize too.
Dec 2 2019
I updated alsa-lib to version 22.214.171.124 (currently at 1.1.9 in the repo) and Borderlands 2 still won't start...
Yeah. Different audio setups might be the case...
Nov 30 2019
Are you still having issues with the games, @aleksvor?
I have a working patch to update openal-soft to the recently released update 1.20.0 that I will send up shortly, but testing borderlands before and after the update show the same issue for me. It just won't start :(
Oct 10 2019
Sep 26 2019
Borderlands 2 runs fine for me now, please re-open if you are having trouble still.
Closing due to lack of response in over 30 days.
Jul 9 2019
OK, I've reinstalled the game on my main partition (it was before on another partition), and the minigames work.
As I said, I've had this issue for a long time, ever since I got the game (over half a year ago), so I've tried all the Proton version with it.
Jul 8 2019
In this case. This is a windows only game, in which it makes use of the proton runtime. I'd check which proton version you're using within steam. And if none of those options work, make a report over at https://github.com/ValveSoftware/Proton/issues
Jul 7 2019
Jul 6 2019
Apr 30 2019
If I could get some command line log information that would help.
Apr 20 2019
Yeah, they look to be the same oddly enough...
I really don't know but looking at the files they are the same with a quick look
erm that stuff is inside steam already or are they different ?