Seeing as this is something Ikey wants to look at, re-assigning to him.

https://dev.getsol.us/R2928:5e7746ca0d5ca7d2ac1d43cf326e2e9d7a15705b

@DataDrake Then probably this can be closed now, if you think LSI should keep going how it is, and this topic can be reassessed if anything changes in the future?

I think the main problem is that there are 2 blacklists now. One done by Valve, where they learn about problems first, and then one in LSI, where we only learn it when someone runs into an issue.
So I think all we could do is find where that blacklist is in https://gitlab.steamos.cloud/steamrt/steam-runtime-tools and monitor it. Then it would be much easier to troubleshoot and understand what Valve is trying to do. And then LSI can live on.
I think the blacklist here, separate depending on which runtime a game is using (scout, soldier or in the future sniper): https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/blob/master/tests/pressure-vessel/inside-runtime.py#L691 and https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/blob/master/tests/pressure-vessel/containers.py#L937

I'm glad to see that Valve are taking this seriously, but I don't think we are quite there yet. Look at how much of a difference in performance there is just for the client with native on and off. It's night and day. I'd love to finally be in a position where it isn't necessary anymore, but I still have quite a few older games that simply will not run without it. And in the 5 years that we've had it, I've only needed to disable it for one game in a library of over 250 titles.

The fix has now been merged into Steam Runtime. This can now be closed.

By the way, the one I had was the 460.67, and before that I had the 390..141

yes, I just tried the terminal and found that my nvidia driver was causing the steam to crash. So after uninstalling my nvidia driver I was able to get steam to load again. I will have to look for a better driver option on my video card. any suggestions? Graphics Processor: GeForce GT 710/PCIe/SSE2

Do you get any interesting output when you launch steam from the terminal?

I have been installing every available update that has been made available to the software center for me to download, the most recent ones were yesterday evening.

Operating System: Solus 4.2
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
OS Type: 64-bit
Graphics Platform: X11
Memory: 7.8 GiB of RAM
Graphics Processor: GeForce GT 710/PCIe/SSE2

When you say you installed the "mandatory security updates" do you mean you didn't install ALL available updates? If so, you should do that and then report if the issue persists.

Using -nostartupmovies -nomovies does actually make the game work. This is great, atleast I can play now.. Many thanks for this workaround.

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.

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.

In T7458#177181, @osgyan wrote:

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

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

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.

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?

It seems to be working fine now (with native runtime and intercept library set to ON).

Is this still an issue?

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.

Yes, it works with native runtime (ON) and the intercept library (OFF).

Does it work in this configuration?

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.

I updated alsa-lib to version 1.2.1.2 (currently at 1.1.9 in the repo) and Borderlands 2 still won't start...

Yeah. Different audio setups might be the case...

In T7458#161538, @Jacalz wrote:

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 :(

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 :(

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.

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.

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

If I could get some command line log information that would help.

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

In T7881#148879, @Girtablulu wrote:

https://dev.getsol.us/source/steam/browse/master/pspec_x86_64.xml$25

erm that stuff is inside steam already or are they different ?

erm that stuff is inside steam already or are they different ?

Hmm, I had no issues running Proton/SteamPlay games with the native runtime so far.

No. LSI uses default settings besides Unity workaround.

Are you forcing 32-bit mode?

@DataDrake here you are.

@aleksvor can you install alsa-lib-dbginfo and update the stacktrace please? thank you.

Seems that issues with Aspyr games aren't resolved still. Borderlands 2 and Civ 5 still segfault on my system, but with different backtraces than before.

Sorry! I'm trying to get this in today. It has been pending because it requires a rebuild of everything using openal

Yeah, I have a differential revision open D5163, but it hasn't been merged yet. @Tzigamm

Any update on this ? ?

I have successfully managed to track down the issue behind this and it seems that the GitHub tarballs are borked, will have a revision up shortly ?

Will have a look at updating openal-soft to 1.19.1 tomorrow to see if that fixes it, I sure hope so...

This issue also effects Civ V and dose not discriminate if you have LSI on or off

@smt Now it works, thank you very much!

I have the same thing too, I found online somewhere that

-nostartupmovies -nomovies