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
- Oh dear - ARC Raiders was logging your private Discord chats [updated]
- Ubuntu and Fedora devs comment on California's new Digital Age Assurance Act
- Many more US states are planning or already have operating system age verification laws
- EA Javelin Anticheat job listing mentions future support for Linux and Proton
- Bazzite gets a big update with KDE Plasma 6.6, Mesa 26.0.1 and more
- > See more over 30 days here
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam DeckRecently Updated
be used in diagnosing problem steam games.
I've never using those before.
Something like "DEBUGGER=gdb steam" only tracks steam and
doesn't follow launched games. Plus, running steam within GDB
will not allow for continued keyboard input at the gdb prompt,
Much like, within bash, running an executable with
ampersand (&) at the end. That will return the bash prompt
to you.
Is this the general idea?
strace steam steam://rungameid/239140