17
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Aug 2025
17 points (94.7% liked)
Linux Gaming
19942 readers
10 users here now
Gaming on the GNU/Linux operating system.
Recommended news sources:
Related chat:
Related Communities:
Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.
founded 5 years ago
MODERATORS
My best guess is that you have an GPU that either doesn't support Vulkan, or has driver issues. But we shouldn't guess, that's what logs are for.
For Steam logs, running Steam from terminal as suggested is one way. Do note that error with wrong ELF class for game overlay library when starting any game is normal, since Steam tries to load both 32 and 64 for bit version for each game, and the wrong one will always fail. Arch wiki has more information.
https://wiki.archlinux.org/title/Steam/Troubleshooting#Debugging_Steam
For Proton logs, set environment variable PROTON_LOG=1. You can do it in Steam launch options, see Proton Readme for more info.
https://github.com/ValveSoftware/Proton?tab=readme-ov-file#runtime-config-options
With hardware and firmware issues system logs often point to right direction. Again Arch wiki has a good tutorial on it.
https://wiki.archlinux.org/title/Systemd/Journal#Filtering_output
Games often have their own logging too if you need to go there. You'll need to look those up, as they vary by game.
I hope this helps.
The issue might be with Vulkan, but I'll check to make sure. Whenever I try to play Black Mesa, it always needs to load Vulkan, despite others saying it only needs to happen once. I'll adjust the Proton logs and use the terminal output for Steam as well and see if I can find the problem(s). Thanks for the help