While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations: 
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
Patreon. Plain Donations: PayPal.This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Linux and open source getting age checking exemptions could be problematic
- Steam Deck stock returns but there's a big price increase
- Proton-CachyOS adds low latency layer and Discord rich presence support
- Dusklight the reimplementation of The Legend of Zelda: Twilight Princess gets a major update
- Flathub moves to ban nearly all apps and submissions made with generative AI
- > See more over 30 days here
Anticheat check - which competitive games actually work on Linux?
How to give Valve feedback when Proton games have issues on Linux / SteamOS- New Desktop Screenshot Thread
- Hamish - Fully native alternative to ProtonDB
- ProfessorKaos64 - Restrict way kernel-level-anti-cheat is installed.
- PlayingOnLinuxphone - Are Mac computers good and stable?
- PlayingOnLinuxphone - Terminal trick - progress indicator in the task manager…
- Shmerl - See more posts
Using nvidia driver 430.14-7, Arch, kde.
Everytime I start up Into The Breach, after a few moments of gameplay, it crashes, and shuts down all my programs and logs me right out to the display manager!
I tried updating Proton (currently 4.2-5) but no luck.. anybody else having issues like this?
Thanks
I would suggest doing proton logging and then reporting to the Proton GitHub.