protonscr

Into The Breach crashes X session with nVidia 430.14

protonclosed appid 590380Game compatibilityNVIDIA drivers
ValveSoftware/Proton#2772 · opened 2019-06-04 by VancouverJohn · updated 2020-04-20 · 5 comments · github · game page · search this game
1 matching comments, n / p to jump
VVancouverJohn 2019-06-04 github

Compatibility Report

  • Name of the game with compatibility issues: Into the Breach
  • Steam AppID of the game: 590380

System Information

  • GPU: GeForce GTX 1050 Mobile
  • Driver/LLVM version: nvidia 430.14-7
  • Kernel version: 5.1.6-arch1-1-ARCH
  • Link to full system information report as Gist:
  • Proton version: 4.2-5

I confirm:

  • [y] that I haven't found an existing compatibility report for this game.
  • [y] that I have checked whether there are updates for my system available.

steam-590380.log

Symptoms

After a few moments of gameplay, the game crashes and takes down the entire X server.

Reproduction

  1. Start Game, go through title and squad selection
  2. Within a few moments of gameplay the game crashes
Kkisak-valve maintainer 2019-06-04 github

Hello @VancouverJohn, this game is rendering with OpenGL and in general no OpenGL application should cause the system-wide issues, which hints that this is a video driver issue. Are there any hints in dmesg that go along with this?

VVancouverJohn 2019-06-04 github

This is the output of my dmesg between crashes.

VVancouverJohn 2019-06-08 github

I found the following logs in journalctl which correspond to the crash of X.

Pperet 2019-06-28 github

I had this same issue on Ubuntu 19.04 with the nvidia-driver-418 package, but not with nvidia-driver-390.

Kkisak-valve maintainer 2020-04-20 github

Hello @VancouverJohn, noted at https://github.com/ValveSoftware/Proton/issues/204#issuecomment-616830044, this game was recently removed from the whitelist, and we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/204#issuecomment-616831409.

Upstream links