ValveSoftware
Linux Mint Runtime Container issue
Your system information
- Steam client version (build number or date): Latest
- Distribution (e.g. Ubuntu): Linux Mint
- Opted into Steam client beta?: No
- Have you checked for system updates?: Yes
- Steam Logs:
- GPU: Nvidia
======================
Proton: 1685026001 experimental-8.0-20230525b
SteamGameId: 291550
Command: ['/home/twig/.steam/debian-installation/steamapps/common/Brawlhalla/Brawlhalla.exe']
Options: {'forcelgadd'}
depot: 0.20230424.48416
pressure-vessel: 0.20230418.0 scout
scripts: 0.20230418.0
sniper: 0.20230424.48416 sniper 0.20230424.48416
Kernel: Linux 5.15.0-72-generic ValveSoftware/steam-for-linux#79-Ubuntu SMP Wed Apr 19 08:22:18 UTC 2023 x86_64
Language: LC_ALL None, LC_MESSAGES None, LC_CTYPE None
Effective WINEDEBUG: +timestamp,+pid,+tid,+seh,+unwind,+threadname,+debugstr,+loaddll,+mscoree
======================
(From what I know this seems to be a proton issue but I'm still gonna report it here)
Steps for reproducing this issue:
- Install a Linux mint iso (this might also happen in other Debian/Ubuntu based distros but I don't know) (as for mint doesn't matter which DE you use)
- Install a game that uses proton
- Realize that the game doesn't boot (The fix to this issue can be found down below)
This is not a good or supportable workaround, and is just as likely to break games as it is to fix them.
Please report an issue to https://github.com/ValveSoftware/steam-runtime/issues and provide a log, so that whatever bug you are seeing can be solved properly.
Passing around workarounds does not give us the information we need in order to solve a problem.
Please report an issue to https://github.com/ValveSoftware/steam-runtime/issues
(no need, the issue has been transferred to there now)
and provide a log, so that whatever bug you are seeing can be solved properly
We'll need this information to be able to make progress on solving this.
Hello @Twig6943, as @smcv noted this workaround is not supportable.
In general we're tracking issues with games run with Proton in the Proton issue tracker, but since you're inclined to think there's an issue with the container environment which Proton is run inside, I've transferred this issue report to the steam-runtime issue tracker for a runtime dev to ponder.
A header only Proton log generally hints that the container environment got setup, and Proton started to run, but something went wrong before the actual game got a chance to start. In addition to the details @smcv is requesting, can you undo any workarounds you tried, completely close Steam, then run steam from a terminal and check if there's any hints in the terminal spew when you tell Steam to start the game?
