3 ms·
> Especially binaries and/or Steam games, things running through Wine can be a pain because standard libraries are in non-standard locations. Steam just works,
by q3k 6y ago
> Especially binaries and/or Steam games, things running through Wine can be a pain because standard libraries are in non-standard locations.
Steam just works, though? I've been running nixpkgs.steam for a while, and it has consistently been the best Steam-on-Linux experience I've had. Precisely because what Steam sees is tightly controlled, and there's no place for accidental DLL/.so hell, and ambient changes to your OS making it into Steam/games breaking its assumptions.
(and for everything else you have steam-run/buildFHSUserEnv)
- stingraycharles 6y agoYeah I’m not sure, I recall something with either Steam or the Blizzard Battlenet. I don’t know exactly what it was, but I do know that I spent a day or two trying to relocate objects in a binary application and I ended up just giving up. Having said this, ostensibly I really like NixOS and I have actually used it as my main desktop for about a year back in 2015.
- pstch 6y agoSteam itself works pretty well, but I've had many games just inexplicably segfault on startup. It's weird because I get the same segfault: - using steam-run - in a FHS user environment - in an LXD container (on this NixOS host) running Debian 10 The same games run fine on a Debian 10 host, all of the libraries the link to are bit-identical to the ones in the LXD container, and I've even tried running the exact same kernel. I'm lost here, as I feel like I've made everything match (at least in the LXD container): the kernel is bit-identical, the games are bit-identical, the libraries they link to are bit-identical. There must be something I'm missing.
- glglwty 6y agoTry strace and look at what the is loaded by ld.so?