Yeah, it’s probably my own fault. I tend to …over-tinker(?) when I have something as deeply customizable as Arch/KDE. Bazzite has saved me from that for the most part, though I do like getting my KDE just right.
But yeah, with large updates I will sometimes get an error about “libalpm” or something, and then when I try to run yay again, the db.lck is present so I have to delete it, blah blah blah… Rollback with timeshift and try again, this time exclude everything but /core and /extra, get those installed, reboot, then install the rest.
This time I got it working pretty quickly due to previous experiences. The worst was the time I did it while not having enough space on my hdd to cover the entire update (but didn’t realize until after it already started). That was a fun day lol.
Timeshift was/is a lifesaver on that laptop. Though I think having it as a fallback did make me a little more reckless with my tinkering… But I’m relatively new to Linux, and that’s how I learn.
I meant the:
one. Might need to put “%command%” after it, but I’m still not 100% sure what that even means and why its there so I dunno.
Edit: I would also check out the entry for the game on ProtonDB if you haven’t already (sorry if someone else has already told you all this elsewhere in the thread) to see if anyone else has had similar issues: https://www.protondb.com/app/949230
I haven’t played C:S2 yet, so I can’t say personally, but it could just be a poorly optimized game.