Missed the point entirely, but okay. Note that I did troubleshoot it. I needed to know that it was a lutris problem to begin with.
Having trouble making something work is not at the same level as an auto-update messing up all of your library at once. All I’m saying is, if we want more adoption of free OSes for uses like gaming, the tools we have for it needs to be version-controlled so less technical people are not completely lost.
Kind of a bad take honestly. Some of us want stuff that just work, especially for their gaming environment. I certainly didn’t expect to spend half a day troubleshooting why my library suddenly didn’t work anymore.
I am using Nobara and lutris was auto-updated through their updating tool. Also if it messed up the defaults in configurations, reverting might not even fix the problem.
Yeah, I had to change the runner (is that the term? my UI is in French) for half my games after the update. I suspect it just changed it on my existing game configurations for no reason.
I had stuff like proton complaining it can’t run 32-bit prefixes, an obscure error saying it couldn’t find gamemode… All fixed when I manually changed the runners.
Quite annoying when somzthing that just used ro work suddenly breaks everything.
I don’t have access to my machine right now, so I can’t check exactly what worked for me. I didn’t have the previous configuration either (the lutris scripts I used to install the games must have done this), so I just tried other options I had for runners. When I checked them they were all set on the last entry on the list.
I think for the 32-bit prefix error I had to choose a wine one instead (probably latest wine-GE).
For others that didn’t show anything but had the gamemode error in logs, I switched to another proton version. I remembered being confused seeing two slightly differently worded entries that looked like latest proton GE, and using the other one worked.