Steam client version (build number or date):
Steam Client Beta 1784934043
Steam Client Stable 1785187029
Distribution (e.g. Ubuntu):
Bug happens on SteamOS in gaming mode, does not happen in desktop mode (even when running within gamescope on desktop)
SteamOS Stable 3.8.16 20260716.1
SteamOS beta 3.8.24 20260716.2
SteamOS main 3.9 20260721.1001
Bug did not happen on Arch linux desktop
Reproduced on Steam Machine and Steam Deck and Legion S Go Linux version.
Did not reproduce on Legion Windows version.
Please describe your issue in as much detail as possible:
Buckshot Roulette (2835570) is intermittently crashing while attempting to create a window. It crashes only with SteamOS running in "gaming mode" - I was able to reproduce in this scenario across multiple devices (Deck, Machine, Legion S Go). I was not able to reproduce the failure in desktop mode, so the bug seems specific to the Steam client version in gaming mode.
I'm attaching a Proton log, as initial investigation indicated that this is a Steam client bug. The suspicious line in the log is: handle_syscall_fault backtrace: --- Exception 0xc0000005 at 0x7fb7aab974ea: /home/deck/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so + 0x284ea (vkQueuePresentKHR + 0x23a).buckshot-roulette-crash.log
Interestingly, I got the same failure (with the same line in the log) when I manually disabled the steam overlay in the properties for the game (on the deck + gaming mode).
I could not reproduce with the native Linux version of the game under the same conditions - the bug only happens when running the Windows version via Proton. I also could not reproduce on the Windows Legion in gaming mode, so the bug seems specific to the Linux version of the steam client.
Since the failure is intermittent, I was able to capture a log where the failure was not triggered under the same circumstances (SteamOS gaming mode on deck with Proton), and I did not see the suspicious line. buckshot-roulette-no-crash.log
Steps for reproducing this issue:
Launch game in SteamOS gaming mode with Proton
Intermittently, game will attempt to create a window and crash before window is fully created
If game loads to main menu, you've gotten past the bug. Repeat step 1 - game usually crashes in <5 attempts.
Your system information
Steam Client Beta 1784934043
Steam Client Stable 1785187029
Bug happens on SteamOS in gaming mode, does not happen in desktop mode (even when running within gamescope on desktop)
SteamOS Stable 3.8.16 20260716.1
SteamOS beta 3.8.24 20260716.2
SteamOS main 3.9 20260721.1001
Bug did not happen on Arch linux desktop
steam-logs.tar.gz
Please describe your issue in as much detail as possible:
Buckshot Roulette (2835570) is intermittently crashing while attempting to create a window. It crashes only with SteamOS running in "gaming mode" - I was able to reproduce in this scenario across multiple devices (Deck, Machine, Legion S Go). I was not able to reproduce the failure in desktop mode, so the bug seems specific to the Steam client version in gaming mode.
I'm attaching a Proton log, as initial investigation indicated that this is a Steam client bug. The suspicious line in the log is:
handle_syscall_fault backtrace: --- Exception 0xc0000005 at 0x7fb7aab974ea: /home/deck/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so + 0x284ea (vkQueuePresentKHR + 0x23a).buckshot-roulette-crash.logInterestingly, I got the same failure (with the same line in the log) when I manually disabled the steam overlay in the properties for the game (on the deck + gaming mode).
I could not reproduce with the native Linux version of the game under the same conditions - the bug only happens when running the Windows version via Proton. I also could not reproduce on the Windows Legion in gaming mode, so the bug seems specific to the Linux version of the steam client.
Since the failure is intermittent, I was able to capture a log where the failure was not triggered under the same circumstances (SteamOS gaming mode on deck with Proton), and I did not see the suspicious line. buckshot-roulette-no-crash.log
Steps for reproducing this issue: