From the logs and system info, the container seems to be working fine, so this might well be genuinely a Proton bug and not a problem with SteamLinuxRuntime or pressure-vessel.
The python3 processes in your screenshot are probably the script that Proton runs to do its initial setup, and it looks as though maybe that setup process is getting stuck somewhere.
If you send SIGTERM to the pressure-vessel-adverb processes (or to all the pressure-vessel processes), that should result in all the leftover processes being terminated, and you can try again.
If Proton wasn't unpacked successfully, you might need to stop the processes as above, then delete its dist/ directory (Proton 5.13/dist) and check the integrity of the rest of Proton (Properties -> Local Files -> Verify Integrity of Tool Files).
This is what it looks like when I try launching one of my games. I waited for 30 minutes, but it would just do nothing.
Here's my log from start to finish: https://gist.github.com/Raklodder/664a6a5cc0e60486d2bfce518c909849
This looks like a Proton issue rather than a pressure-vessel issue. @kisak-valve, please could you move this to Proton, so people who know more about how Proton starts up can ask for the correct information?
I have a similar issue on Ubuntu 20.04 . I can provide more logs/ info if needed. i get a similar failure message from every log. This is the log from Cyberpunk 2077 but the same error occurs in Among us, 7 days, Phasmaphobia and every other game
ERROR: ld.so: object '/home/john/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/john/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/john/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/john/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
esync: up and running.
ERROR: ld.so: object '/home/john/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
10266.401:0028:002c:trace:loaddll:build_module Loaded L"C:\windows\system32\ntdll.dll" at 000000007BC00000: builtin
10266.406:0028:002c:err:module:import_dll Loading library kernelbase.dll (which is needed by L"C:\windows\system32\kernel32.dll") failed (error c0000020).
wine: could not load kernel32.dll, status c0000135
10266.408:0020:0024:err:environ:run_wineboot failed to start wineboot c0000135
10266.413:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\ntdll.dll" at 7BC00000: builtin
10266.423:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\kernelbase.dll" at 7B000000: builtin
10266.424:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\kernel32.dll" at 7B620000: builtin
10266.430:0020:0024:trace:loaddll:build_module Loaded L"C:\Program Files (x86)\Steam\steam.exe" at 7EA40000: builtin
10266.464:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\ucrtbase.dll" at 7E880000: builtin
10266.464:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\sechost.dll" at 61B00000: builtin
10266.464:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\advapi32.dll" at 7E980000: builtin
10266.472:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\gdi32.dll" at 7E720000: builtin
10266.481:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\rpcrt4.dll" at 6FDC0000: builtin
10266.508:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\version.dll" at 65980000: builtin
10266.508:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\setupapi.dll" at 6A900000: builtin
10266.508:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\user32.dll" at 7E4F0000: builtin
10266.508:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\ole32.dll" at 65200000: builtin
10266.543:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\shcore.dll" at 64B40000: builtin
10266.543:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\shlwapi.dll" at 68C40000: builtin
10266.543:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\shell32.dll" at 7DAE0000: builtin
10267.346:0020:0024:trace:loaddll:build_module Loaded L"C:\windows\system32\imm32.dll" at 6C0C0000: builtin
10267.388:0034:0038:trace:loaddll:build_module Loaded L"C:\windows\system32\ntdll.dll" at 000000007BC00000: builtin
10267.393:0034:0038:err:module:import_dll Loading library kernelbase.dll (which is needed by L"C:\windows\system32\kernel32.dll") failed (error c0000020).
wine: could not load kernel32.dll, status c0000135
Setting breakpad minidump AppID = 1091500
Steam_SetMinidumpSteamID: Caching Steam ID: 76561197990401795 [API loaded no]
10267.421:0020:0030:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
10267.421:0020:0030:err:winediag:nodrv_CreateWindow The explorer process failed to start.
10267.470:0020:0024:err:steam:run_process Failed to create process L""S:\common\Cyberpunk 2077\REDprelauncher.exe"": 1115
pid 10827 != 10826, skipping destruction (fork without exec?)
Hello @Raklodder, wine: could not load kernel32.dll, status c0000135 and the path to the game hints that you've encountered an NTFS-related issue like #4269 and not the hanging process described here.
To be clear, if you are not seeing a potentially stuck python script as described in this issue report, then this issue report is not for you.
Nothing is work at all with Proton for me, not any game at all with Proton
I also have to end up killing/ending the processes related to soldier and pressure vessel as they don't end and it just consumes memory every launch attempt
Might as well remove the games if there is no fix soon
How can I roll back the Proton update that broke all my steamplay games from launching?
The select specific runtime option doesn't show each minor version just majors
I tried purging the latest update of 5.13 and soldier runtime and reinstalling it, that did not fix it, I am still unable to load ANY SteamPlay enabled games on Proton
I would also like to be able to download a specific minor version so I can rollback please to an earlier 5.13 minor release
I suggest people take local backups and only manually update Proton after taking a backup each time, turn off auto update or you end up with a potentially broken update and no recovery
How can we DISABLE auto update on Proton and Soldier?
I only see
????) DISABLE?????? WHERE IS THIS CHOICE?
WHERE IS DISABLE AUTO UPDATE? COME ON
You broke my system, and you won't let me 1) roll back to a minor version prior, and 2) you won't let me DISABLE auto update
COME ON!
Not sure who is worse, Microsoft or Valve now (if you use Steam, it is no longer your machine it seems) I thought Valve was Linux friendly, not with these update choices you're not
This was no minor update when you break our system
I have a backup of a working Proton version, you keep overwriting it with the broken version by forced updates
Hello @jjanedoh, none of the feedback you've given hints that you're seeing the same issue as reported here. Please open a new issue report with logs.
Hello @jjanedoh, none of the feedback you've given hints that you're seeing the same issue as reported here. Please open a new issue report with logs.
Can you tell me how to DISABLE auto update so I can restore my backup of Proton that works?
I am getting lots of launcher pressure vessel and processes stuck like this bug since the -4 update
I need to restore my backup but you keep overwriting it with forced updates
https://www.reddit.com/r/SteamPlay/comments/kbw1mk/steam_proton_5134_not_launching_games/
More people with problems
Tell me how to disable auto update and I go away
What is the point of me backing up stuff when you overwrite it with forced updates anyway?
When I restore my backup Proton 5.13 from earlier pre -4 update on launch you update it to the broken one
Why bother with backup and restore?
You're worse than Microsoft
You should be ashamed of yourself for forcing updates
How hard is it to add a "DO NOT AUTO UPDATE" option to the properties update tab and globally?
@jjanedoh, you're clearly more interested in venting your frustration instead of helping figure out this issue and have been given a 24 hour timeout for your behavior. Please do not spam comments in the future.
Looks like I got the same issue like @Raklodder,
Every game i've tested with Proton 5.13 refuses to finish the initial setup of the wineprefix via the python-script.
But I am running a Manjaro installation, and im wondering, what im doing wrong, since the are some report on ProtonDB saying, that it runs on thier manjaro system. Here are my System-Informations: https://pastebin.com/b7hY2JzD
Hi,
After recent update games via Proton getting stuck at preparing to launch Temtem window and not generating any proton logs.
I tried to switch to proton 5 but still the same.
If I directly switch to 5.13 to 5.0 without deleting "compathdata/<game_ID>/pfx" (P.S. it remove your save file, take backup) game won't launch but if I delete "pfx" after setting to 5.0 and restart steam game launch without any issue. (This is kind of strange.)
Steam Terminal log 5.0 without deleting
proton 5.13 is getting stuck at preparing to launch window due to python script execution.
Steam Terminal log 5.13
I've got the same proton, soldier runtime & pressure-vessel related problem on Fedora 34 (beta) and I'm again stuck with 5.0.
The initial game installation either don't start, installed games don't run and/or can't fully close on game or client exit.
proton 5.13x5 2020-12proton 5.13-4x1 2020-12proton 5.0x1 2020-12kernel32.dllx2 2020-12advapi32.dllx1 2020-12gdi32.dllx1 2020-12imm32.dllx1 2020-12kernelbase.dllx1 2020-12ntdll.dllx1 2020-12ole32.dllx1 2020-12rpcrt4.dllx1 2020-12sechost.dllx1 2020-12setupapi.dllx1 2020-12shcore.dllx1 2020-12shell32.dllx1 2020-12shlwapi.dllx1 2020-12ucrtbase.dllx1 2020-12user32.dllx1 2020-12
I've not been able to launch any game with Proton 5.13 on Fedora 33 since launch. Tested Quake Champions (2017), Quake IV (2005) and various of other installed games and reinstalled my system with the same result. Additionally on application exit, a ton of leftover processes such as bwrap, pressure vessel, etc. seems to run indefinitely until I shut down my system.
https://i.imgur.com/0GXXlxS.png
System information:
Steps for reproduce: