Is this really that rare? Maybe it’s because I pretty much exclusively game on Linux but I feel like I see that message rather often.
On a side note I feel like Linux gamers could help each other out by mentioning how well the game works with Proton in their review. Also if there’s any tweaks you need to do like using a specific version or bugs you encountered.
It doesn’t need to effect the over all review. Good to know though.
Oh yeah I typically check there and the PCGamingWiki if I run into difficulties but it’s nice to not have to leave the Steam store page. Though admittedly I should probably check ProtonDB anyway in case an update caused a game to stop working with Proton.
i think it would be a good thing to also mention it on an normal steam review because that could mean that other user switch to linux that would have not because they think thair games don’t run on linux
Rasies hand. Finally jumping back into Linux after years of Windows. Didn’t really think of the gaming impact other than “so many games don’t work on Linux so I can’t use my main machine.” I’m lucky enough to have 3 computers currently even though 1 of them is a third gen i7 and the other I got for free out of the trash so it’s specs aren’t great either. Enoug for me to install Endeavor then Mint to see how it goes gaming on them.
@ono I thought protondb reports brought you closer to what you were looking for. IDK if sifting through uncurated steam reviews would be helpful without Steam first implementing such filters that would remove all other reviews.
Ok so I’ve fixed it, appears to have been an issue with the tool having come from my backup rather than installed directly.
couldn’t uninstall due to “missing shared content” so i deleted the file and verified integrity so it downloaded them - everything is now running perfectly, tried a few different games and they are working great.
but that’s awesome you figured it out and shared the solution here. There’s nothing about this out there that is searchable. Thanks for the learning lesson!
Somewhere late in the Proton 5.x cycle (I think it was 5.13) Valve introduced Steam Runtime version 2: Soldier, which uses bubblewrap containers to solve various problems with host system libraries, but also broke some things. For example, it wants a newish version of bwrap and no longer works inside most other containers (except for Flatpak, which added special functionality to accommodate it).
If you’re not using your own containers, I imagine upgrading to a recent version of Linux Mint might help, by giving you a newer version of bubblewrap, and/or enabling user namespaces (which bwrap uses) if they weren’t already enabled.
Alternatively, if you’re comfortable running code from Flathub, you might consider using the Steam flatpak instead of your distro’s native package.
Once upon a time, Flathub also had community-built versions of Proton that were stripped of their container functionality. I don’t know if those are still maintained.
If you could show an error message in the terminal either I or another person could help you. I’m guessing you’ve already searched the internet for a solution since you went through the painful process of re-installing the whole nine. What a marathon you’re running! Anyway, to run steam game in the terminal, you have to know the game id, which is a long number. If I’m correct (someone, if this is wrong, please correct me!), you would type something like this in the terminal: steam steam://rungameid/{YourGameID}
Yeah, the glaring “permissions denied” is right smack in the middle of all that. Then it just continues like that to the very end. One thing that makes no sense to me: manually changing the permissions on every single game. I’m a basic Linux boy and I do basic things, so don’t do what I’d do. What I’d try doing: changing the permissions in the .steam folder to the correct permissions, applying them to all the enclosed files and folders. I’d even have the stones to do it in the graphical UI left clicking on the .steam folder out of sheer basic laziness. My solution is totally basic and dumb, because it does not foresee new games being acquired through steam, which could revert back to the erroneous permissions. I searched for the error message to see what is relevant, nobody is reporting this problem, so, you’re unique. What a way to feel special, right? I’ll keep looking shit up like you’re doing. While we’re busy with that, someone more competent will come to your rescue, for sure.
It’s possible they installed with sudo or something, which ruined the permissions. First try find /home/lewis/.steam ! -user lewis. That will show if any files got owned incorrectly. If so, do chown -R lewis:lewis /home/lewis/.steam.
Not sure this is a permission/owner issue though. My guess is /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point: 285: exec: /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/run doesn’t have the executable bit. try chmod +x /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point: 285: exec: /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/run.
VRR works fine in Proton and on Plasma’s Wayland compositor. I don’t think the game supports VRR, as I saw reports of windows users lamenting that the game doesn’t support it either.
This is my experience too. However, there is nothing special a game needs to do to support VRR. So the fact that VRR works fine in this game under Windows but not Linux makes me think there is a bug in Proton, the compositor, or the GPU driver.
I can say with 100% certainty that VRR is working as expected under Windows 11 with my RTX 3080. I haven’t tested in Fedora yet.
linux_gaming
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.