Latest Steam update broke it under Solus

Fiona_1986

Harvey Thanks for the reply, maybe I will check it out in a couple of days, since I am not around at the weekend. Usually I try to avoid the flatpak version of steam because for some reason few titles only playable with the Proton compatibility layer have problems with the Wayland communication protocol. That's not the case with the "native" steam client/installation provided by the package manager, at least that's what I experienced in the last couple of months.

Fiona_1986

Harvey After some tinkering around I can finally confirm that the updated flatpak version of the steam client runs flawlessly under Solus 4.5.

VTMarik

Fiona_1986 I can't seem to get it to launch a single game, do you have any specific settings in place?

SethStorm666

VTMarik

I'm using the Steam from the repositories, works fine here. Try run it via the terminal and see if anything useful shows up.

VTMarik

I figured my problem out, it was a problem with Steam not playing nicely with the NTFS drive that my games are installed to.

[deleted]

Are you using SSD or HDD? What are your specs?

The possible cause in some cases is too slow disk I/O:
https://github.com/ValveSoftware/steam-for-linux/issues/10581

Friedell

Well,since months nothing happenend with this issiue,despite several OS updates
i still get the same errormessage when trying to start Steam in Solus.
"Steamwebhelper not responding"

zmaint

Friedell I've not had any Steam issues with the repo version, but I'm using Plasma and Nvidia with X. Not sure if any of that makes any difference for your case. If you're using Nvidia, make sure to check the 32 bit library box in DoFlicky (hardware driver manager) when you install the driver or Steam will not launch.

Have you tried launching steam from terminal? Post the output here, that might help track down the issue.

Staudey

Friedell Yes, this has not been fixed yet in Steam. The issue is still open.

https://github.com/ValveSoftware/steam-for-linux/issues/10556

nolan

zmaint Solus uses the source that Valve provides (my guess), and the fix is not jet released (probably they are working on it) from Valve, I use Steam from flatpak and it works, I haven't used it from several day ago though, will try it wen I have time.

MikeK61

I`m also affected by this issue but what confuses me most is that steam still runs under Budgie.DE.

alfisya

MikeK61 on the same computer? Because this problem is hardware dependant. It only affects older PC CPU that miss some instruction set archictecture (ISA) that most of modern/newer CPU have.

MikeK61

alfisya

Yep, same computer and same Solus installation.
For some reason i have Plasma and Budgie.

nolan

MikeK61 For some reason i have Plasma and Budgie.

Friedell

From what ive read it has something to do with glibc-hwcaps and the way the steamsoftware
looks for certain libraries. Before the Steamupdate in late february all was fine because Steam
was able to find this libraries in Solus. After the update it only finds the V3 version and that
causes the steamwebhelper crash on older CPUs. In my case a FX8350.

Friedell

alfisya Well,so far nothing has changed since my initial posting. And basicly it excludes all
CPU`s that doesnt support the AVX2 instruction set from using Steam under Solus (and many other distros).
And its only Steams own webhelper app that seems to need this instructions under Linux,because the same
hardware works perfectly fine under old Win7 to this day.

[deleted]

Friedell You can work around that by using the unofficial Steam Flatpak.

Friedell

Well,since last friday Steam works again. With the last Steamclientupdate came the possibility
to circumvent hwcaps with a inbuild hack in Solus.
Its activated by tipping into the terminal : echo "STEAM_HACK_IGNORE_HWCAPS=1" | sudo tee /etc/environment
Than log out and log in again,then tipp in terminal:
Run sudo ldconfig -X

It works for the time being at least,but i guess future Steamupdates will refine it.