this post was submitted on 30 Apr 2025
43 points (100.0% liked)
Linux Gaming
18417 readers
183 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME
away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Hm this part of the log doesn't look like the error. Those messages usually show up after the process has crashed. If there is nothing that looks like it's gamecrash related to you further above in the log, type
sudo dmesg --follow
in a terminal. This display the logs of all device drivers on a kernel level. While that is open, start the game and wait for it to freeze and see if any errors show up.Also, if you post log messages again please put them in a
by typing it like this:
```
codeblock
```
Should be more readable. If the log is rather long just put it into a pastebin or some other text sharing service.
Okay will do. And yes because I had to Force Stop it through steam rather than it crashing on its own I didn't see any super helpful logs. I will try the command you sent when I am able!
When you run steam from the terminal, you want to use -d to get the debugging info: