protonscr

Properties panel crash with A Plague Tale when selected custom proton is deleted

steamclosed Steam clientProton
ValveSoftware/steam-for-linux#6986 · opened 2020-03-25 by cherryroots · updated 2021-03-19 · 12 comments · github
Ccherryroots 2020-03-25 github

Your system information

  • Steam client version (build number or date): 2020-03-23 build
  • Distribution (e.g. Ubuntu): Arch - Manjaro
  • Opted into Steam client beta?: [Yes/No] Yes
  • Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

When deleting a custom proton version that is assigned to the game A Plague Tale, steam will crash when opening the properties panel for the game. However the same does not happen when I do the same for Streets of Rogue, then the "Force the use of a specific Steam Play compatibility tool" option just gets unchecked and no crash happens.

/home/zuriele/.local/share/Steam/steam.sh: line 722: 186600 Segmentation fault (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"

Can provide dmp file of the crash if needed

Steps for reproducing this issue:

  1. Set A Plague Tale to use custom proton
  2. Delete the custom proton version and restart steam
  3. Open steam and open the properties panel for the game
  4. Steam should crash to desktop
Kkisak-valve maintainer 2020-03-25 github

Previously mentioned at https://github.com/ValveSoftware/steam-for-linux/issues/6757#issuecomment-603311283.

Ccherryroots 2020-03-25 github

Regarding that comment, it can be repaired by going into the steamfolder/config/config.vdf and setting the CompatToolMapping name for the appid to "" (blank) which disabled the compattool and let me access the properties menu again without crashing

Ssoredake 2020-04-04 github

Happens again with GTA IV

Mmferraci 2020-04-13 github

I have same issue when deleting custom proton version on Black Mesa, The Surge and Worms Armageddon

Regarding that comment, it can be repaired by going into the steamfolder/config/config.vdf and setting the CompatToolMapping name for the appid to "" (blank) which disabled the compattool and let me access the properties menu again without crashing

I confirm deleting all inside CompatToolMapping is a valid workaround

4414n 2020-05-14 github

I observed this too for Warframe, but not for Dragon Ball Fighter Z.

LLordJABA 2020-06-11 github

AFK it happens for every game that had a specific Proton version that was later removed specified. It should just revert to "use global" in such case, I think.

TTerryvanderjagt 2020-06-18 github

After encountering this bug, Steam removed my game files making me re-download all 75GB of Borderlands 3. :) Is this a side effect of this bug that other users are encountering as well, or is this a different issue?

DDragoonAethis 2020-07-28 github

Same here, here's the client crash dump: crash_20200728194752_1.zip

Rromulasry 2020-09-19 github

Removing compattoolmapping fixed it, but it is still a bug.

Ssoredake 2021-02-10 github

This seems to be fixed with steam ui update, it does not crash anymore.

DDragoonAethis 2021-02-13 github

Yep, no longer crashes - just leaves the "force the use of a specific Steam Play compatibility tool" checkbox off.

Kkisak-valve maintainer 2021-03-19 github

Closing per the last couple comments.

Upstream links