You may actually be having to wait on Steam to download a different version of proton, once downloaded sometimes it can take time for the prefix to be generated 'automatically reconfigured for the corresponding proton version' and the accompanying run-time's to install for a particular game. Sometimes you will have to delete a prefix in rare cases and re-run everything with a particular version of proton. Sometimes they can be pretty slow to get fully up and working. On Slackware stable for the life of me I could not get Warhammer 40k Boltgun running during the course of a day, everything was already setup, I had it running on Slackware current just fine. I gave up and tried the next day and it ran just fine on stable as well, I think Steam was behind on downloading something or another, it can seem anomalous at times but all games end up working. Some games install and get set up faster than others too. I mostly use GloriousEggroll but the times I tried Steams default versions it can take time to download and Steam to be aware that it's downloaded and installed.

Now for the 'too long didn't read' but for those who have a piqued interest in case you want to proceed down this sort of Steam wrap.

I have 195 titles installed and anything I pick runs. Game install automation and prefix generation can be annoyingly slow, flatpak or repository Steam doesn't seem to matter. Of those titles there are some that have Easy Anti-Cheat, I can play Ironsight just fine. I don't think there is actually anything that I can't run to be honest. I have about 300 games, rarely I will have to use protontricks and use a custom setup, it's usually on older games that are known to even give Windows users issues. Surprisingly I actually think I have better luck getting certain games running that Windows users can't, especially with Lutris which is a whole other animal yet awesome.

I hope I have not gave bad advice and just have happened to have good luck on my end. There are some caveats but not what I would consider major from my own experience. There is a small learning curve to some things, hopefully this stuff ends up working just as well for those of you that are trying it as it has for me.

There are only a few annoying things I can say about the flatpak version of Steam, 1.) When you go to a games properties then select installed files then click on browse, it will pick easytag as a file manager or konqueror 'they still show the game location', my workaround is to note the game location and go to the same place by using thunar or dolphin. 2.) Having to add extra drives for accessing Steam libraries already existent through flatseal or flatpak command line.

I do know that I'm not the only one using Steam flatpak on Slackware, I have seen other people post on reddit and other places saying it's awesome. I hope it's not a YMMV thing but what I said, just a bit of a learning curve.

This might not actually have to do with flatpak but make sure Steam shuts down properly if you have Steam game libraries on other drives, sometimes you will have to re-add them if you don't which can be annoying to do. I believe I had the same issue on Manjaro if I remember correctly. Steam is a massive and complex chunk of software, there is always going to be jank of some sort. KDE's compositor integrates the best with Steam, say for instance you are looking at the Steam store and then switch work spaces and then come back to Steam, KDE won't have a black blank screen like it will with XFCE, the solution for XFCE is to click on your library in the interface and then switch back to the store.

After everything being set up, I do actually prefer the flatpak over repository packages. Over both Manjaro's and Artix's Steam packages. I actually had command line installed Artix running S6 and it's Plasma desktop was nowhere near as snappy as Slackware's.

Lastly, depending on how a live disk is made and for what purposes, some live distributions can be finicky when it comes to installing and running certain things, if it's a thumb drive image that behaves like a SSD and stores whatever changes you make? You might be alright, it's just going to be slowwwwwwwwww, even after much of it is loaded into your RAM.

I had my doubts and negative feelings about using the Steam flatpak, I felt it was iffy, the wrong kind of stodgy, and backed up like a stopped up plumbing line, I didn't feel it was complete as I wanted it to be. So I spent some time with it, I thought ok, so I can't part with Slackware no way in hell, I am going to deal with this cause I already knew how a lot of other distributions are and more time and patience was spent learning the ins and outs of flatpak and now I don't want to part with this version of Steam. Everything feels really solid and tightly bolted together with thread-lock. All of us Slackware users and Slackers are different at the end of the day though, sometimes diametrically opposed different.

Which version of flatpak are you using? Dunno if that matters but alienbob's current directory has

FYI the latest legacy Nvidia-470.239.06 drivers work well with the new 6.7.6 kernel, without needing patch.

1 members found this post helpful.