Four days ago, I woke up, as I usually expect to after going to sleep and I turned on my really fucking awesome Archlinux gaming rig, hit the desktop and decide, hmmmm... I haven't updated in a while(a week), let's pacman -Syyuu and get up to speed. Well, I got up to speed and my favorite game, the best game of all time, Team Fortress 2
##FAILED TO LOAD! ๐ ๐ฅ
In the imminent crisis-state that I had found myself in, I did what any filthy scout-main Archlinux user would do, I googled the problem and put the word arch in quotation marks.
The first five results yielded ancient bullshit useful to someone five years ago, probably. The next ten, redditors complaining about old tat. Then I did what any old wine veteran would do. I shut steam down and started it in the terminal so I could monitor its raging bitch-fit in real time.
Team Fortress 2 failed to load because of lib32-libtcmalloc.so. Arch had updated it to a future version not yet even coded, and steam wasn't having it. The answer was on protondb all along! So, some fella says
The native version of tcmalloc introduced a bug on TF2 that it randomly crashes the game. You need to install lib32-gperftools (name of the Arch AUR package, other distros should have similar names) and add LD_PRELOAD=/usr/lib32/libtcmalloc.so %command% to your launch options to override the library.
et voila, I'm torturing 25/7 2fort.
Now, I know what you're thinking, who in their right mind would suggest Archlinux for a beginner? See, that's where I already caught you because this bug trickles all the way down to Garuda and Manjaro users too since they have the same libraries (and that fancy SteamOS that's floating around).
So while I love Linux and software freedom, I find suffering Linux on someone might be more suited to a person that actually wants it, and not to work through it to get to what they actually wanted to do.
I wanted to play Team Fortress 2, and I was rather irate about the last thing on my steam account that shouldn't work, not working all over me. This system has been a saint for six months, but when it's a devil, boy, is it.
Anyway, KDE is better than gnome! Thanks for reading!
You should change your Distribution. Arch is a rolling release distribution with a strong focus on customization. If you use binaries shipped by another source, problems like those you described are quite likely to happen. Going to a distribution that isn't that cutting edge (but still cutting edge enough to deliver working drivers/libs) would reduce the risk for such things.