TF2 Crash on loading any map (Fresh Bazzite/PC; doesn't happen on Fedora/PC or Bazzite/Deck-OLED)
Hey, just installed bazzite to try it on my PC after some experience with it on my Deck-OLED. Installed Team Fortress 2 first thing to test and it crashes to desktop whenever the game would normally load into a map. This doesn't happen on my regular PC/Fedora:39 (gnome) or my Deck-OLED/Bazzite:latest (gaming mode). Anybody else experiencing this or have any idea what might be happening?
I used to get an issue with identical behavior on Fedora, but back then the logs said something about LD PRELOAD and the workaround was to symlink a specific library inside the game folder. That issue was resolved with TF2's recent 64-bit update, and the crash logs I see now mention a bus error at ./tf.sh:83 instead of anything LD PRELOAD.
This issue persists whether I run using steam's Sniper Linux runtime or Proton.
AMD 6700XT + AMD 5800X3D
Solution:Jump to solution
i also can't access any network services when I host them on the old installation. I think the system must be mangled somehow, despite supposedly being an atomic image that should prevent this class of issues. I'm gonna just wipe the drive and reinstall fresh again.
7 Replies
No launch options, no set compatibility tool



not using legacy
main menu

in-game without issue

Weird
I have another spare drive, I'm gonna try installing bazzite on it and see if the issue persists across both installs
alright. it doesn't. im baffled.
I did have an old image for the first install and had to apply the key fix before running topgrade. Other than that, the second time around I skipped the welcome portal, installing flatpaks, and moving around kde widgets. I'm not sure what would cause this inconsistency
Solution
i also can't access any network services when I host them on the old installation. I think the system must be mangled somehow, despite supposedly being an atomic image that should prevent this class of issues. I'm gonna just wipe the drive and reinstall fresh again.