ValveSoftware / ValveSoftware/Proton

Steam client waiting on worker thread stalled by a Proton 8.0 and MangoHUD interaction

Open
#6,809 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

Your system information
  • Steam client version (build number or date): 1682708537 apr 28
  • Distribution (e.g. Ubuntu): Arch
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
Please describe your issue in as much detail as possible:

Steam client fails to shut down. This happens on an almost fresh install of Steam (What I mean by this is that I deleted the whole "root" folder and the Linux dependencies with all versions of Proton, except for "steamapps") explicitly after installing all the runtimes for Linux Gaming such as Proton, Sniper, Soldier and Steam Frameworks.
Maybe it is correlated with the fact that Proton 8 is not working on my machine? I'm dumbfound at this point as to why this is a thing, but it's driving me crazy. Both problems have been a thing for a while on my system out of nowhere.

Steps for reproducing this issue:
  1. Install Steam using the official AUR repo
  2. Check SteamPlay button
  3. Install Steam dependencies such as the ones mentioned above.
  4. Try to install and play a game using proton 8?
  5. Try to shut down Steam
  6. See task manager, type "Steam", now you have extra processes that weren't there before not wanting to shut down.
    2023-29-05-2

Update: Yes, just INSTALLING Proton 8, or even Proton GE 8-3/Experimental hangs Steam indefinitely. if I delete Proton 8 it gets fixed. This doesn't happen with Proton 7 installed.
What's going on with Proton 8? first version ran fine on my machine, but now it doesn't open any game and makes Steam not-shut down.

Another update: This is a mangohud related issue it seems.
I checked the logs when I tried playing a game with Proton 8 and it showed a lot of config files from mangohud that were not found.
I don't know which is to blame, but deleting mangohud fixes proton 8 which fixes the client issue.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the reproduction steps and the reported updates about Proton 8, Proton GE 8-3/Experimental, and MangoHUD. Compare the behavior with Proton 7 and without MangoHUD using the described Arch installation. Done means the responsible interaction is identified and the Steam shutdown and game-launch behavior are no longer affected.

Written by the indexing model from the issue text.

Assessment

Domain
game-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.