Steam Issues after April 8/9 Update - Solution

T3RR0RH4WK

So I am glad about not being the only one to experience this issue. I posted something similar on Reddit on the Back 4 Blood subreddit because when the game added Proton support I was interested in testing, but then quickly found out I had to open LSI to turn off Native Runtime in order to get the game to even launch.

Hope a fix is incoming. I can't use my Steam Overlay while using Steam's binaries, so I lose half the functionality I would normally have.

Reddit post about it:

528491

The dev task linked by JacekJagosz helped me:

The workarounds are to use the steam runtime or remove/mask /usr/lib32/haswell/libc.so.6 (reinstall glibc-32bit to get the file back, it will fallback to /usr/lib32/libc.so.6 instead)

T3RR0RH4WK

528491 I do use Steam Runtime now for this game and for Insurgency: Sandstorm, however I now have no Steam Overlay which kinda sucks, cause I have to tab out of the games to invite friends or respond to message now.

528491

T3RR0RH4WK
I removed /usr/lib32/haswell/libc.so.6 and can launch Ubisoft Connect with native runtime again.

T3RR0RH4WK

528491 I tried this as well, and I still have no Steam Overlay while using Steam Native through LSI. The EAC / Back 4 Blood splash comes up and shows an Overlay prompt as well as displays Steam's in-game FPS counter at the top left, but once the game launches it shows nothing and Overlay cannot be brought up. Weird...

528491

T3RR0RH4WK

joebonrichie I am actually afk for a few weeks now

Guess you have to wait :/

T3RR0RH4WK

528491 Lol I saw that comment, too, so yep... looks like I'll await further investigation. So far I've found that only online games have this, and they happen to be EAC titles. I play Star Wars Battlefront II (2017) online and through native and it works just fine.

JacekJagosz

When this gets accepted at least the overlay with the Native Runtime OFF should be fixed at least. Unfortunately even though I spend many hours playing with LSI's code I still couldn't fix issues with Native ON and /usr/lib32/haswell/libc.so. But it should get a bit better.
If you need a fix before the next friday sync, here is the .eopkg.

JacekJagosz

@joebonrichie Just fixed haswell/libc.so issue too! So with the next Friday sync all Steam-related things should just work™

Flo

Hello there !
I just updated today and for me the problem is getting worse...
I can't launch game now with "use native runtime" ON or OFF, neither by changing the proton version nor using proton-GE.
Am I the only one ? Does somebody have a solution ?
By the way, before that I wasn't able to play with my gamepads in steam (ds4 and xbox one tested) while native runtime were desactivated.
Thanks for any answer !

My specs :
AMD ryzen 5 2600
Nvidia gtx 1060 6GB
Fresh install of solus, with today updates

zmaint

Flo Sometimes deleting the prefix will help. I've found that bouncing around between different proton versions, especially between standard proton and a custom proton like GE, that prefix gets corrupted. It lives in the compatdata folder under the game ID. Just be warned, sometimes this folder also will house your saved games, so back those up before deleting it. Steam will auto generate the folder on next game launch.

JacekJagosz

Flo Could you add in game preferences LD_PRELOAD='/usr/$LIB/libxcb.so.1:/usr/$LIB/libX11.so.6:/usr/$LIB/libstdc++.so.6' %command% and try to launch it? This is the only thing that changed with the last updates, I removed it, I really hoped it wouldn't cause any problems.
Also maybe launch steam via terminal and see if there is any output that could point to the problem.

Flo

zmaint

JacekJagosz
I'm so so so so so so SO SORRY.. I forgot to install the 32bit version of nvidia current driver while reinstalling solus..
Thus I feel a bit stupid.
Everything works great now, thanks for the update, all the work with solus, and thanks for your (wasted) time 😅

zmaint

Flo Glad you got it working and posted the solution!

JacekJagosz

Flo No problem, we all make mistakes!