Proton 5.13 breaks all non-Linux games

[afettouhi]

As the title says. I have tried to run several games now with the new Proton 5.13 and nothing works. Titles tested so far are Doom Eternal, Torchlight, Stealth Inc. 2, Dear Esther: Landmark Edition & The Messenger. All these titles work fine on Proton-5.0-9.

Below is the terminal output when running steam on Arch and launching the game Torchlight

[af@andre ~]$ /usr/bin/steam-runtime %U
Running Steam on arch rolling 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
Steam client's requirements are satisfied
/home/af/.local/share/Steam/ubuntu12_32/steam %U
[2020-10-16 18:18:41] Startup - updater built Oct 15 2020 19:00:58
[2020-10-16 18:18:41] Opted in to client beta 'publicbeta' via beta file
You are in the 'publicbeta' client beta.
Installing breakpad exception handler for appid(steam)/version(1602795778)
[2020-10-16 18:18:41] Loading cached metrics from disk (/home/af/.local/share/Steam/package/steam_client_metrics.bin)
[2020-10-16 18:18:41] Using the following download hosts for Public, Realm steamglobal
[2020-10-16 18:18:41] 1. http://media4.steampowered.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf'
Installing breakpad exception handler for appid(steam)/version(1602795778)
[2020-10-16 18:18:41] Verifying installation...
[2020-10-16 18:18:41] Verification complete
Loaded SDL version 2.0.13-6142881
/usr/share/themes/Adapta-Nokto-Eta/gtk-2.0/common-dark-eta.rc:1425: error: unexpected identifier 'direction', expected character '}'
/usr/share/themes/Adapta-Nokto-Eta/gtk-2.0/3rd-party-dark-eta.rc:475: error: invalid string constant "toolbar", expected valid string constant
Installing breakpad exception handler for appid(steam)/version(1602795778)
STEAM_RUNTIME_HEAVY: ./steam-runtime-heavy
[1016/181843.465415:INFO:crash_reporting.cc(247)] Crash reporting enabled for process: browser
[1016/181843.483890:WARNING:crash_reporting.cc(286)] Failed to set crash key: UserID with value: 0
[1016/181843.483934:WARNING:crash_reporting.cc(286)] Failed to set crash key: BuildID with value: 1602788454
[1016/181843.483937:WARNING:crash_reporting.cc(286)] Failed to set crash key: SteamUniverse with value: Public
[1016/181843.483940:WARNING:crash_reporting.cc(286)] Failed to set crash key: Vendor with value: Valve
[1016/181843.510793:WARNING:crash_reporting.cc(286)] Failed to set crash key: UserID with value: 0
[1016/181843.510833:WARNING:crash_reporting.cc(286)] Failed to set crash key: BuildID with value: 1602788454
[1016/181843.510837:WARNING:crash_reporting.cc(286)] Failed to set crash key: SteamUniverse with value: Public
[1016/181843.510839:WARNING:crash_reporting.cc(286)] Failed to set crash key: Vendor with value: Valve
[1016/181843.511255:INFO:crash_reporting.cc(247)] Crash reporting enabled for process: gpu-process
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)
[1016/181843.704262:WARNING:crash_reporting.cc(286)] Failed to set crash key: UserID with value: 0
[1016/181843.704299:WARNING:crash_reporting.cc(286)] Failed to set crash key: BuildID with value: 1602788454
[1016/181843.704304:WARNING:crash_reporting.cc(286)] Failed to set crash key: SteamUniverse with value: Public
[1016/181843.704307:WARNING:crash_reporting.cc(286)] Failed to set crash key: Vendor with value: Valve
[1016/181843.704749:INFO:crash_reporting.cc(247)] Crash reporting enabled for process: utility
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)
Warning: failed to set thread priority: set failed for 8: -1: setpriority() failed
Warning: failed to set thread priority: set failed for priority 8
Warning: support for elevated priorities is most likely unavailable, suppressing future warnings
Warning: failed to set thread priority: set failed for 8: -1: setpriority() failed
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)
CApplicationManagerPopulateThread took 157 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
Installing breakpad exception handler for appid(steam)/version(1602795778)
Proceed to auto login
Installing breakpad exception handler for appid(steam)/version(1602795778)
CAppInfoCacheReadFromDiskThread took 475 milliseconds to initialize
Installing breakpad exception handler for appid(steam)/version(1602795778)
Opted-in Controller Mask for AppId 0: 0
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)

(steam:46409): Gtk-WARNING **: 18:18:44.823: gtk_disable_setlocale() must be called before gtk_init()
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)
roaming config store loaded successfully - 10427 bytes.
migrating temporary roaming config store
BRefreshApplicationsInLibrary 1: 55ms
[1016/181848.281281:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
[1016/181848.342645:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
[1016/181848.414847:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
Installing breakpad exception handler for appid(steam)/version(1602795778)
Failed to init SteamVR because it isn't installed
ExecCommandLine: "'/home/af/.local/share/Steam/ubuntu12_32/steam' '%U'"
System startup time: 7.46 seconds
[1016/181849.241270:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
Warning: failed to set thread priority: set failed for 4: -1: setpriority() failed
Warning: failed to set thread priority: set failed for priority 4
Warning: support for elevated priorities is most likely unavailable, suppressing future warnings
[1016/181849.251282:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
Warning: failed to set thread priority: set failed for 4: -1: setpriority() failed
Warning: failed to set thread priority: set failed for priority 4
Warning: support for elevated priorities is most likely unavailable, suppressing future warnings
BuildCompleteAppOverviewChange: 1443
RegisterForAppOverview 1: 51ms
RegisterForAppOverview 2: 53ms
[41500]Non-Steam Controller Configs Enabled: 1
Installing breakpad exception handler for appid(steam)/version(1602795778)
Opted-in Controller Mask for AppId 41500: 0
GameAction [AppID 41500, ActionID 1] : LaunchApp changed task to ProcessingInstallScript with ""
_v2-entry-point[46582]: STEAM_COMPAT_APP_ID=41500
_v2-entry-point[46582]: STEAM_COMPAT_SESSION_ID=eb0927d8afd4e1b0
_v2-entry-point[46582]: XDG_RUNTIME_DIR=/run/user/1000
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
_v2-entry-point[46624]: STEAM_COMPAT_APP_ID=41500
_v2-entry-point[46624]: STEAM_COMPAT_SESSION_ID=eb0927d8afd4e1b0
_v2-entry-point[46624]: XDG_RUNTIME_DIR=/run/user/1000
bwrap: Can't mkdir /usr/lib32/gconv: Read-only file system
ln: kunne ikke oprette symbolsk lænke '/run/user/1000/SteamLinuxRuntime.eb0927d8afd4e1b0/socket' -> '': Ingen sådan fil eller filkatalog
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
bwrap: Can't mkdir /usr/lib32/gconv: Read-only file system
ln: kunne ikke oprette symbolsk lænke '/run/user/1000/SteamLinuxRuntime.eb0927d8afd4e1b0/socket' -> '': Ingen sådan fil eller filkatalog
_v2-entry-point[46738]: STEAM_COMPAT_APP_ID=41500
_v2-entry-point[46738]: STEAM_COMPAT_SESSION_ID=eb0927d8afd4e1b0
_v2-entry-point[46738]: XDG_RUNTIME_DIR=/run/user/1000
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
_v2-entry-point[46788]: STEAM_COMPAT_APP_ID=41500
_v2-entry-point[46788]: STEAM_COMPAT_SESSION_ID=eb0927d8afd4e1b0
_v2-entry-point[46788]: XDG_RUNTIME_DIR=/run/user/1000
bwrap: Can't mkdir /usr/lib32/gconv: Read-only file system
ln: kunne ikke oprette symbolsk lænke '/run/user/1000/SteamLinuxRuntime.eb0927d8afd4e1b0/socket' -> '': Ingen sådan fil eller filkatalog
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
_v2-entry-point[46864]: STEAM_COMPAT_APP_ID=41500
_v2-entry-point[46864]: STEAM_COMPAT_SESSION_ID=eb0927d8afd4e1b0
_v2-entry-point[46864]: XDG_RUNTIME_DIR=/run/user/1000
bwrap: Can't mkdir /usr/lib32/gconv: Read-only file system
ln: kunne ikke oprette symbolsk lænke '/run/user/1000/SteamLinuxRuntime.eb0927d8afd4e1b0/socket' -> '': Ingen sådan fil eller filkatalog
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
bwrap: Can't mkdir /usr/lib32/gconv: Read-only file system
ln: kunne ikke oprette symbolsk lænke '/run/user/1000/SteamLinuxRuntime.eb0927d8afd4e1b0/socket' -> '': Ingen sådan fil eller filkatalog
/data/src/clientdll/installscript_posix.cpp (419) : Assertion Failed: Standalone evaluator returned error code for app 41500
/data/src/clientdll/installscript_posix.cpp (419) : Assertion Failed: Standalone evaluator returned error code for app 41500
Installing breakpad exception handler for appid(steam)/version(1602795778)
assert_20201016181855_27.dmp[46976]: Uploading dump (out-of-process)
/tmp/dumps/assert_20201016181855_27.dmp
GameAction [AppID 41500, ActionID 1] : LaunchApp changed task to SynchronizingCloud with ""
GameAction [AppID 41500, ActionID 1] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 41500, ActionID 1] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 41500, ActionID 1] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 41500, ActionID 1] : LaunchApp continues with user response "CreatingProcess"
Game update: AppID 41500 "", ProcID 46978, IP 0.0.0.0:0
ERROR: ld.so: object '/home/af/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/af/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/af/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Starting app 41500
>>> Adding process 46978 for game ID 41500
GameAction [AppID 41500, ActionID 1] : LaunchApp changed task to WaitingGameWindow with ""
>>> Adding process 46979 for game ID 41500
pid 46981 != 46979, skipping destruction (fork without exec?)
ERROR: ld.so: object '/home/af/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
GameAction [AppID 41500, ActionID 1] : LaunchApp changed task to Completed with ""
_v2-entry-point[46979]: STEAM_COMPAT_APP_ID=41500
_v2-entry-point[46979]: STEAM_COMPAT_SESSION_ID=eb0927d8afd4e1b0
_v2-entry-point[46979]: XDG_RUNTIME_DIR=/run/user/1000
ERROR: ld.so: object '/home/af/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 46980 for game ID 41500
>>> Adding process 46982 for game ID 41500
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
ERROR: ld.so: object '/home/af/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
>>> Adding process 46983 for game ID 41500
>>> Adding process 46984 for game ID 41500
>>> Adding process 46985 for game ID 41500
bwrap: Can't mkdir /usr/lib32/gconv: Read-only file system
ln: failed to create symbolic link '/run/user/1000/SteamLinuxRuntime.eb0927d8afd4e1b0/socket' -> '': No such file or directory
ERROR: ld.so: object '/home/af/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
ERROR: ld.so: object '/home/af/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
pressure-vessel-launch[47058]: Can't connect to peer socket: Could not connect: No such file or directory
>>> Adding process 47057 for game ID 41500
>>> Adding process 47058 for game ID 41500
Game removed: AppID 41500 "", ProcID 46978 
Uploaded AppInterfaceStats to Steam
assert_20201016181855_27.dmp[46976]: Finished uploading minidump (out-of-process): success = yes
assert_20201016181855_27.dmp[46976]: response: CrashID=bp-c6eb6988-1cc7-4974-b6b0-5e21f2201016
assert_20201016181855_27.dmp[46976]: file ''/tmp/dumps/assert_20201016181855_27.dmp'', upload yes: ''CrashID=bp-c6eb6988-1cc7-4974-b6b0-5e21f2201016''
Exiting app 41500
No cached sticky mapping in ActivateActionSet.Installing breakpad exception handler for appid(steam)/version(1602795778)
Installing breakpad exception handler for appid(steam)/version(1602795778)

I am using the latest KDE desktop and the latest Nvidia driver with a 1080 EVGA GTX card btw.

[frostworx]

Just downloaded Torchlight and tried to reproduce this on my Arch system.
The game works without any issues with Proton 5.13-1 here.
Is it possible that you have vkBasalt, Mangohud enabled? They currently have compatibility problems with the Steam Linux Runtime, which is autostarted with Proton 5.13-1.
I released steamtinkerlaunch 2.4.0 some hours ago, which allows to disable the Steam Linux Runtime _(and does so automatically if conflicting tools are enabled)_ _(removed the automation)_
Maybe worth a try.

[techmouse]

I'm also having the same problem, and by an interesting coincidence, I'm also on the latest KDE.

KDE Neon

EDIT: I don't know if it helps, but the exact error I'm getting from the console is:
No cached sticky mapping in ActivateActionSet.No cached sticky mapping in ActivateActionSet.

[PixelByte21]

i am having this issue as well. if there is any info someone needs let me know.

Running Linux Mint

[kisak-valve]

Hello @frostworx, please be aware that Proton 5.13 has substantially newer baseline requirements from being built against the Soldier runtime instead of the Scout runtime. By running Proton 5.13 outside of Soldier, you or the end user will be responsible for any (mainly missing or incompatible dependencies) issues encountered while outside of the intended runtime environment, which is likely on most installs with a little age on them.

[frostworx]

Hi kisak, of course. This should be obvious for every custom tweak applied to Proton, shouldn't it?

[afettouhi]

@frostworx No, I don't use vkBasalt or Mangohud. I am using steamtinkerlaunch for the Giana Sisters games but for the games I mentioned steamtinkerlaunch isn't used.

[gardotd426]

Is it possible that you have vkBasalt, Mangohud enabled? They currently have compatibility problems with the Steam Linux Runtime, which is autostarted with Proton 5.13-1.

This isn't the issue. Games still run with MangoHud/vkBasalt enabled, it's just that MangoHud and vkBasalt just don't work. The game runs as if they aren't enabled. It doesn't prevent games from running.

I will also add that I can't reproduce this issue on Arch Linux, I'm able to run games with Proton 5.13 just fine.

[afettouhi]

Is it possible that you have vkBasalt, Mangohud enabled? They currently have compatibility problems with the Steam Linux Runtime, which is autostarted with Proton 5.13-1.

This isn't the issue. Games still run with MangoHud/vkBasalt enabled, it's just that MangoHud and vkBasalt just don't work. The game runs as if they aren't enabled. It doesn't prevent games from running.

I will also add that I can't reproduce this issue on Arch Linux, I'm able to run games with Proton 5.13 just fine.

Very strange that this works on your Arch system without issue.

[gardotd426]

I mean not really, I've seen a large number of other users test out Proton 5.13 with no issue, you seem to be the only few.

[afettouhi]

Yeah, but the output I posted doesn't really tell us why I am having this issue. Other than this for example

bwrap: Can't mkdir /usr/lib32/gconv: Read-only file system

[gardotd426]

Doom Eternal running fine...

[gardotd426]

I've also tested Titanfall 2 and a few other games, haven't had an issue as of yet.

[gardotd426]

That read-only error is pretty bizarre, though.

[afettouhi]

That read-only error is pretty bizarre, though.

Yep!

[gardotd426]

That directory is owned by lib32-glibc, which just got an update like yesterday or the day before, have you updated lately? I just checked, last update was Oct 14th, day before yesterday.

That shouldn't really make a difference, but I do know glibc is like, of the utmost importance, so it could be worth checking to see if it's up to date.

[afettouhi]

My system is completely up 2 date.

[gardotd426]

Do you have steam-native-runtime installed by chance?

If so, you need to uninstall it.

[afettouhi]

Yes, I have that installed? Why do I need to uninstall it?

[gardotd426]

Numerous reasons, but for right now, because it's breaking the Steam Linux Runtime and you aren't supposed to use it.

The Arch Wiki itself tells you not to use it.

Warning: Using the Steam native runtime is not recommended as it might break some games due to binary incompatibility and it might miss some libraries present in the Steam runtime.

https://wiki.archlinux.org/index.php/Steam/Troubleshooting#Steam_native_runtime

Uninstall it, and your games will work.

But if you really want to know, when you install the steam-native-runtime package (which you're not supposed to do), it disables the bundled Steam runtime. If you go into Steam, and then click "Help" -> "System Information" and then scroll down to the "Steam Runtime" bit, it'll say "runtime disabled."

Well that's no good, because Proton 5.13 depends on the Steam Linux Runtime.

steam-native-runtime disables the bundled Steam runtime and tries to run everything from the system files. It's not intended for general use, and only for troubleshooting for people who know what they're doing, and definitely not with Proton 5.13.

steam-native-runtime is not a package for regular end users. Uninstall it.

[afettouhi]

OK, I will uninstall it and try testing some of the games I tried before to see if it makes a difference.

[gardotd426]

If it's not obvious already, make sure you fully exit steam and restart it after uninstalling it.

[andrew-mcmahon]

I guess I'm sort of lucky...
Debian Testing with Linux 5.9

_Default Mesa 20.19 - OK_

steam.log | steam-570940.log | steam_system_info.log

---

_Mesa 20.3-devel - NOPE_ :-1:

MESA_GIT_steam.log | MESA_GIT_steam-570940.log | MESA_GIT_steam_system_info.log

So I guess it's a PATH issue with the new runtime not finding my Vulkan driver in a custom location?
I know that the newer driver is working; not had this problem before with Proton.
environment.log | glxinfo.log | vulkaninfo.log

---

edit: in order to use mesa-master I had to comment out:
VK_ICD_FILENAMES=/opt/mesa/share/vulkan/icd.d/radeon_icd.i686.json:/opt/mesa/share/vulkan/icd.d/radeon_icd.x86_64.json

[afettouhi]

Just tested Torchlight and Stealth Inc. 2 and they still won't launch with Proton 5.13.

[gardotd426]

Just tested Torchlight and Stealth Inc. 2 and they still won't launch with Proton 5.13.

I wouldn't be surprised if you don't even have the Steam Runtime Soldier installed considering you had steam-native-runtime installed this whole time.

Now that you've removed it, go to Help -> System Information, and scroll down to the fourth section, where it says "Operating System Information." The last line of that section should say Steam Runtime Version: steam-runtime_0.20201005.0

[TheDunkShot]

Ok so I did what @gardotd426 said to do, It now runs... kinda, COD: IW says that steam needs to be running and shows it in a generic wine popup.

[gardotd426]

COD: IW says that steam needs to be running and shows it in a generic wine popup.

Sounds like it's looking for Steam.exe to be running, which is a known issue with some games.

Seems Valve didn't fully vet compatibility for the new titles as much as they thought. TKG's Proton builds include a fix for that very issue, but his builds also don't have the new stuff that COD:IW needs to run, so that's not a viable alternative for that game.

You need to post on the issue thread for that specific game, and test known-working ones as far as this thread is concerned.

[afettouhi]

Just tested Torchlight and Stealth Inc. 2 and they still won't launch with Proton 5.13.

I wouldn't be surprised if you don't even have the Steam Runtime Soldier installed considering you had steam-native-runtime installed this whole time.

Now that you've removed it, go to Help -> System Information, and scroll down to the fourth section, where it says "Operating System Information." The last line of that section should say Steam Runtime Version: steam-runtime_0.20201005.0

No Steam Runtime Soldier is installed and the system information is saying steam-runtime_0.20201005.0.

[TheDunkShot]

@gardotd426 weird because someone got COD: IW to work with Proton 5.13-1
www.youtube.com
I want to know how he got it to work or if he had to run/do anything for it to work out of the box.

[gardotd426]

Let me buy it real quick and I'll let you know.

On Fri, Oct 16, 2020 at 5:10 PM TheDunkShot [e-mail]
wrote:

@gardotd426 https://github.com/gardotd426 weird because someone got
COD: IW to work with Proton 5.13-1
www.youtube.com https://www.youtube.com/watch?v=DLfOnP7cjKA
I want to know how he got it to work or if he had to run/do anything for
it to work out of the box.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-710640137,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y33ZNV2PWM72DTXKI7ITSLCZGFANCNFSM4STRMDRA
.

[TheDunkShot]

Weird, ok so Proton 5.13-1 folder was there but steam deleted the files, using Proton 5.13-1 on steam at that point was a Wine passthrough, btw its still brokey.
Its not starting at all now like it was before.
EDIT: Ok so, I removed Steam Runtime Linux - Soldier and it also deleted everything inside Proton 5.13-1. back to the "isn't running steam." and whenever IT downloads steam runtime linux - soldier it immediately crashes on boot with any game.
EDIT2: Ok so, Proton 5.13-1 didn't nuke itself this time but steam linux runtime soldier needs 199 files reacquired but it still comes up with the same popup.
EDIT3: Running the game with Soldier ends up with the same bug as running it with Proton 5.13-1, removing wine-staging from my system makes the game not start up at all.

[gardotd426]

Well, I'm downloading the game, but I didn't realize ActiBlizz started the
"100GB CoD Downloads" 4 years ago lmao, so I'm gonna have to amend the
"real quick" part. I'll test it tonight or tomorrow (probably tomorrow) and
report back.

On Fri, Oct 16, 2020 at 5:24 PM TheDunkShot [e-mail]
wrote:

Weird, ok so Proton 5.13-1 folder was there but steam deleted the files,
using Proton 5.13-1 on steam at that point was a Wine passthrough, btw its
still brokey.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-710653516,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y333JPP74HPUGPX5GXZTSLC22DANCNFSM4STRMDRA
.

[TheDunkShot]

Yeah whats weird is that, running the game through Proton 5.13-1 and Soldier ends up at the same point. I'm starting to wonder if it's a wine issue.
Ok, I uninstalled wine-staging, and I'm strictly using only proton now, and its not working either.

[zelfir]

I probably have the same issue.
I'm running Pop_OS 20.04 with a RTX 2060 and drivers 455.28.
Games I've tried with Proton 5.13.1:

• The elder scrolls online -> the launcher starts but the game gives me a black screen (works with proton 5.9)
• Control -> Also a black screen (works with proton 5.9)
• Dishonored -> Works perfectly as before
  So far only Dishonored worked (it's probably using an older DX version, which may be a hint).

[gardotd426]

Dishonored uses DX9, so I guess that's possible. Elder Scrolls Online apparently uses DX11, and Controll has both DX11 and DX12 renderers.

But that still doesn't explain why I'm able to run DX11 games with Proton 5.13-1. I've already tested Titanfall 2.

[gardotd426]

I just tested Hitman 2 DX11, it works fine as well. Though there is something interesting of note.

In the little launch splash menu where you can go over graphics options before launching, official Proton builds show my GPU as a GTX 470. But custom Proton-tkg builds show it as an RTX 3090 (which is correct). Anyone know why that is?

It's obviously not nvapihack, because 1, it shows that even when DX12 is selected, and nvapihack is a DXVK thing, and 2, nvapihack reports Nvidia GPUs as AMD, so it wouldn't show up as a GTX 470. So why on earth do official Proton versions cause the card to be reported as a 470 while Proton-TKG show it as the card it actually is?

[kisak-valve]

Wine needs to be taught what the marketing name of new video cards are, and wine's generic DirectX 11 era nvidia card is reported as a GTX 470 at https://source.winehq.org/git/wine.git/blob/0c249e6125fc9dc6ee86b4ef6ae0d9fa2fc6291b:/dlls/wined3d/directx.c#l879. Once upstream wine is taught about your card, then it'll start being reported correctly. It shouldn't really matter since it's a cosmetic label and shouldn't affect performance.

[LordSocky]

I wouldn't be surprised if you don't even have the Steam Runtime Soldier installed considering you had steam-native-runtime installed this whole time.

Now that you've removed it, go to Help -> System Information, and scroll down to the fourth section, where it says "Operating System Information." The last line of that section should say Steam Runtime Version: steam-runtime_0.20201005.0

The Steam runtime is only disabled if you launch with steam-native instead of steam-runtime. You get both options. I had steam-runtime-native installed and by launching with steam-runtime I still got steam-runtime_0.20201005.0 in my system information.

For testing purposes I removed it anyways, rebooted fully and tried again. Still nothing. No version of Proton currently works for me. Yes, I have Steam Runtime Soldier installed. I even uninstalled and reinstalled it just to be absolutely certain it was in working order. Native games work fine, even when I force enable Steam Runtime Soldier for those games. It is only Proton that is broken, and in my case, it's completely broken. Some users seem to be able to revert to older versions, but not all of us can.

[gardotd426]

@kisak-valve oh absolutely, it doesn't affect performance whatsoever, I was just really, really confused as to why the disparity, but now that you mention this it makes so much sense, because Wine 5.13 was out before the 3090 released, and the TKG build I'm using is based on Wine 5.17, so yeah, that makes total sense

[gardotd426]

The Steam runtime is only disabled if you launch with steam-native instead of steam-runtime. You get both options. I had steam-runtime-native installed and by launching with steam-runtime I still got steam-runtime_0.20201005.0 in my system information.

No, you don't. Not by default.

If you install steam-native-runtime, it disables the Steam Linux Runtime automatically. You have to install Linux Steam Integration to toggle them (or you can use envvars and whatnot, but by default it disables the runtime).

And either way, there is absolutely no reason to ever use steam-native-runtime if you're just an end user, there's a reason the Arch Wiki explicitly says not to use it. Everyone I've ever seen try and use it has only ever had issues, and it has no benefit.

Everyone praises the Arch Wiki until it says something they don't feel like doing lol.

[kisak-valve]

@gardotd426, that's true for Manjaro's packaging, but not Arch's packaging. Arch's packaging provides two launcher scripts: steam-native and steam-runtime with separate application entries for the DE and they behave exactly as expected.

[tomaszg7]

I'm having similar problem on Gentoo. Proton 5.13 doesn't run anything. There were a couple of hurdles in my case.

• The first was the lack of XDG_RUNTIME_DIR variable.
• The second was the lack of bwrap package.

After fixing both issues, Proton games work for me again. Note that these things were not needed before.

[Arucard1983]

So far any game that uses Proton 5.13 both on Ubuntu 20.04 or Debian 10 are not working, even using the XDG_RUNTIME_DIR variable trick.

[afettouhi]

I'm having similar problem on Gentoo. Proton 5.13 doesn't run anything. There were a couple of hurdles in my case.

* The first was the lack of `XDG_RUNTIME_DIR` variable.

* The second was the lack of `bwrap` package.

After fixing both issues, Proton games work for me again. Note that these things were not needed before.

I have both of these things already done but still Proton 5.13 won't run anything.

[gardotd426]

I'm having similar problem on Gentoo. Proton 5.13 doesn't run anything. There were a couple of hurdles in my case.

* The first was the lack of `XDG_RUNTIME_DIR` variable.

* The second was the lack of `bwrap` package.

After fixing both issues, Proton games work for me again. Note that these things were not needed before.

I have both of these things already done but still Proton 5.13 won't run anything.

Well what errors are you getting now? I doubt it's the bwrap error anymore, if you have bubblewrap installed

[afettouhi]

I'm having similar problem on Gentoo. Proton 5.13 doesn't run anything. There were a couple of hurdles in my case.

* The first was the lack of `XDG_RUNTIME_DIR` variable.

* The second was the lack of `bwrap` package.

After fixing both issues, Proton games work for me again. Note that these things were not needed before.

I have both of these things already done but still Proton 5.13 won't run anything.

Well what errors are you getting now? I doubt it's the bwrap error anymore, if you have bubblewrap installed

Same errors. These things have been installed/set for a long time on my system.

[gardotd426]

Paste a full log in gist.

On Fri, Oct 16, 2020 at 9:57 PM André Fettouhi [e-mail]
wrote:

I'm having similar problem on Gentoo. Proton 5.13 doesn't run anything.
There were a couple of hurdles in my case.

• The first was the lack of XDG_RUNTIME_DIR variable.

• The second was the lack of bwrap package.

After fixing both issues, Proton games work for me again. Note that these
things were not needed before.

I have both of these things already done but still Proton 5.13 won't run
anything.

Well what errors are you getting now? I doubt it's the bwrap error
anymore, if you have bubblewrap installed

Same errors. These things have been installed/set for a long time on my
system.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-710725425,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y334FDUQHRXVL3WK3CITSLD2Z7ANCNFSM4STRMDRA
.

[oblitum]

I have been using steam-native for literally many years and until today it rarely broke on me, actually using the non-native version broke so often back then that the native solution for Arch was more stable, reason why I've stick to it, until now. Today I've installed Proton 5.13 and seems I can't launch Batman Arkham Knight anymore, I didn't test other games, and I've been reading this thread, from my experience with steam-native, tagging it as a can of worms is mostly just bulshit, but anyways, I've uninstalled it completely, including steam, then just steam again (I confirm that on Arch I could launch either version, native or not, but I rarely used non-native for a very long time), still, no dice, the game won't launch with the same list of errors as posted here already:

/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
_v2-entry-point[83476]: STEAM_COMPAT_APP_ID=208650
_v2-entry-point[83476]: STEAM_COMPAT_SESSION_ID=d851cdd524c72ad4
_v2-entry-point[83476]: XDG_RUNTIME_DIR=/run/user/1000
bwrap: Can't mkdir /usr/lib32/gconv: Read-only file system

etc....

[afettouhi]

Paste a full log in gist.
…
On Fri, Oct 16, 2020 at 9:57 PM André Fettouhi @.*> wrote: I'm having similar problem on Gentoo. Proton 5.13 doesn't run anything. There were a couple of hurdles in my case. * The first was the lack of XDG_RUNTIME_DIR variable. * The second was the lack of bwrap package. After fixing both issues, Proton games work for me again. Note that these things were not needed before. I have both of these things already done but still Proton 5.13 won't run anything. Well what errors are you getting now? I doubt it's the bwrap error anymore, if you have bubblewrap installed Same errors. These things have been installed/set for a long time on my system. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4278 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y334FDUQHRXVL3WK3CITSLD2Z7ANCNFSM4STRMDRA .

https://gist.github.com/afettouhi/40362f16c782913fe3ceef23b6bfb909

[gardotd426]

from my experience with steam-native, tagging it as a can of worms is mostly just bulshit

Go ahead and take that up with the Arch Wiki.

There's a reason why they tell people not to use it.

Legitimately 75% of the time I'm trying to help someone on an Arch-based distro having issues with Proton, it turns out they were using steam-native-runtime, and going back to regular Steam fixed it.

And now, the Steam runtime is a hard dependency of Proton, so it's moot anyway.

As far as these bwrap/gconv errors, it's bizarre because I have zero mention of any of those from any of my logs, where games are working fine. bwrap and gconv are not mentioned once in any log (not even a success message).

The only common thread I've seen so far with Arch-based users at least, is that people having issues were previously using steam-native-runtime. I don't know if running Steam like that when the Soldier runtime was installed caused it to not get installed correctly or what, but using steam-native-runtime is the only commonality I see so far for Arch users, and it's not an Arch bug or anything because games work fine for me.

[gardotd426]

@afettouhi that log is a bit messy with other stuff, just add PROTON_LOG=1 %command% to the launch options for the game, and then you'll have a file in your home directory called ~/steam-<appid>.log with the appid being the numerical appid for the game. Add that envvar, then try to launch the game, then upload the file or paste it to gist.

[gardotd426]

Also @afettouhi please add LC_ALL=C along with PROTON_LOG=1, so the output is in English.

[afettouhi]

@afettouhi that log is a bit messy with other stuff, just add PROTON_LOG=1 %command% to the launch options for the game, and then you'll have a file in your home directory called ~/steam-<appid>.log with the appid being the numerical appid for the game. Add that envvar, then try to launch the game, then upload the file or paste it to gist.

I tried that for every game, generating a proton but no log is created.

[oblitum]

I just sigh that is a hard dep, wtf, this has been running smooth for so long, on all my machines..... literally sigh. This will probably make me go back to the time their damn runtime got into broken states, missing key libs or something for a given game (200+ games here), which was the cause I've moved to steam native for good.

[gardotd426]

@afettouhi that log is a bit messy with other stuff, just add PROTON_LOG=1 %command% to the launch options for the game, and then you'll have a file in your home directory called ~/steam-<appid>.log with the appid being the numerical appid for the game. Add that envvar, then try to launch the game, then upload the file or paste it to gist.

I tried that for every game, generating a proton but no log is created.

If you actually did it right, and there are legitimately no logs, then you have something seriously wrong with your installation.

It should create a log even if it immediately crashes. Try with a working proton version and see if you get a log. Just launch a game and go to the menu and exit and see if you get a log

[gardotd426]

I just sigh that is a hard dep, wtf, this has been running smooth for so long, on all my machines..... literally sigh. This will probably make me go back to the time their damn runtime got into broken states, missing key libs or something for a given game (200+ games here), which was the cause I've moved to steam runtime for good.

They did this for a reason. And it makes sense. The vast majority of people are praising this move, as it's necessary to get Proton to the next level of compatibility. Of course there are going to be teething issues in a situation like this. But this is off topic.

[oblitum]

I meant steam native, not steam runtime, I fixed the typo before your answer.

[oblitum]

I won't even post my logs, it seems I've hit the exact issue as reported here, so I'll wait what happens in this thread as I could possibly just going to provide duplicated info.

[gardotd426]

That's not true.

If you post logs with the exact same crash, then Valve will be able to fix
it (or help you fix it) that much faster.

If it's a different error, then that would indicate there are multiple
issues, which is important to know. Post a gist.

>

[afettouhi]

@afettouhi that log is a bit messy with other stuff, just add PROTON_LOG=1 %command% to the launch options for the game, and then you'll have a file in your home directory called ~/steam-<appid>.log with the appid being the numerical appid for the game. Add that envvar, then try to launch the game, then upload the file or paste it to gist.

I tried that for every game, generating a proton but no log is created.

If you actually did it right, and there are legitimately no logs, then you have something seriously wrong with your installation.

It should create a log even if it immediately crashes. Try with a working proton version and see if you get a log. Just launch a game and go to the menu and exit and see if you get a log

I just switched Torchlight to using Proton version 5.0-9 and it runs plus the log file is created. But running anything with Proton 5.13 nothing happens. No log file, no installation of directx dependencies etc. No idea why this is happening.

[gardotd426]

It shouldn't need to reinstall the directx dependencies or other first-time setup, as you already have a wineprefix with that stuff.

But still, it should definitely be creating a log.

@oblitum, here's a perfect opportunity. afettouhi can't get a log to even be created, so see if you can reproduce. Add PROTON_LOG=1 %command% to the launch options, try to launch the game, then get the ~/steam-.log file and paste it to gist, or if one doesn't get created, say so.

[oblitum]

Just gonna report that "Steam Linux Runtime - Soldier", whatever it is, is tagged as a game instead of a tool inside the library, which makes it confusing to look up. Whether it's a game or tool in fact, I have no idea, looks like another mistake or something from Valve.

[gardotd426]

Can you try to get the log please?

[afettouhi]

It shouldn't need to reinstall the directx dependencies or other first-time setup, as you already have a wineprefix with that stuff.

But still, it should definitely be creating a log.

@oblitum, here's a perfect opportunity. afettouhi can't get a log to even be created, so see if you can reproduce. Add PROTON_LOG=1 %command% to the launch options, try to launch the game, then get the ~/steam-.log file and paste it to gist, or if one doesn't get created, say so.

I don't think it reinstalls the directx dependencies. With Proton 5.13 I doesn't to be able to even get to that point when launching the game.

[gardotd426]

I don't think it reinstalls the directx dependencies. With Proton 5.13 I doesn't to be able to even get to that point when launching the game.

It doesn't need to reinstall anything, is what I'm saying. You should only need to install the DirectX dependencies once, unless you delete the pfx.

[clarfonthey]

I can confirm that this still doesn't work for me. On Arch Linux, and when running via steam-runtime with Proton 5.13 I get the unfortunate message:

/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so

Note: the game I tested this on was Ikenfell.

[gardotd426]

@clarfonthey What are the three or four lines after that error?

Also, can you please try and get a log by adding PROTON_LOG=1 %command% to the launch options for the game?

[clarfonthey]

@gardotd426 Sure. Except, I've read a lot of these logs before and most of the other linker errors show up in other native games but they don't fail to start.

Starting app 854940
>>> Adding process 270190 for game ID 854940
GameAction [AppID 854940, ActionID 1] : LaunchApp changed task to WaitingGameWindow with ""
>>> Adding process 270192 for game ID 854940
>>> Adding process 270193 for game ID 854940
GameAction [AppID 854940, ActionID 1] : LaunchApp changed task to Completed with ""
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
>>> Adding process 270195 for game ID 854940
>>> Adding process 270196 for game ID 854940
pressure-vessel-wrap[270204]: Cannot run bwrap: wait status 256
pressure-vessel-wrap[270204]: Diagnostic output:
bwrap: No permissions to creating new namespace, likely because the kernel does not allow non-privileged user namespaces. On e.g. debian this can be enabled with 'sysctl kernel.unprivileged_userns_clone=1'.

ln: failed to create symbolic link '/run/user/1000/SteamLinuxRuntime.c85f84434d2073c3/socket' -> '': No such file or directory
ERROR: ld.so: object '/home/ltdk/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 270197 for game ID 854940
>>> Adding process 270198 for game ID 854940
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
ERROR: ld.so: object '/home/ltdk/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
pressure-vessel-launch[270214]: Can't connect to peer socket: Could not connect: No such file or directory
>>> Adding process 270213 for game ID 854940
>>> Adding process 270214 for game ID 854940
Game removed: AppID 854940 "", ProcID 270190
Uploaded AppInterfaceStats to Steam
Exiting app 854940
No cached sticky mapping in ActivateActionSet.Opted-in Controller Mask for AppId 0: 0
Opted-in Controller Mask for AppId 0: 0
Opted-in Controller Mask for AppId 0: 0

(Should clarify, I did add PROTON_LOG=1.)

[gardotd426]

@andrew-mcmahon @Arucard1983 Look at this message from the log above

bwrap: No permissions to creating new namespace, likely because the kernel does not allow non-privileged user namespaces. On e.g. debian this can be enabled with 'sysctl kernel.unprivileged_userns_clone=1'

Try running that command and see if that fixes it. @clarfonthey you should maybe try to, since that's the problem everyone seems to be having.

I'm running a custom kernel which might explain why I'm not having any issues, I can try with a vanilla Arch kernel later.

[gardotd426]

Everyone, when I ran sudo sysctl -n kernel.unprivileged_userns_clone, I got 1 as the output, which might very well explain why I'm not having issues.

Run that command, and if you get a 0 instead of 1, that's your problem, and you need to run sudo sysctl kernel.unprivileged_userns_clone=1.

[afettouhi]

@clarfonthey is a log file created in your case when you add PROTON_LOG=1 with Proton 5.13?

[gardotd426]

@afettouhi run that command I listed above and see what the output is.

sudo sysctl -n kernel.unprivileged_userns_clone.

If it's a 0, that's likely your problem.

[afettouhi]

@afettouhi run that command I listed above and see what the output is.

sudo sysctl -n kernel.unprivileged_userns_clone.

If it's a 0, that's likely your problem.

Just ran that and I get a 1, so it is not that.

[clarfonthey]

@gardotd426 Oh, yeah, I'm also running linux-hardened. I have literally never encountered something like this, though, and it seems like a giant, gaping security hole that Proton would require this setting being enabled.

Especially because they know it's disabled by default on Debian and the like.

It appears to work with that flag turned on but I still consider this a bug. It's basically like asking a user to enable nopasswd sudo for every program on their computer.

[gardotd426]

It's not quite that bad, but I don't completely disagree.

@kisak-valve, can you please look into this? It seems like this is legitimately a bug or a huge security flaw.

@afettouhi, it's really starting to look like you have other issues with your installation.

[oblitum]

Fixed it on my side.

[afettouhi]

It's not quite that bad, but I don't completely disagree.

@kisak-valve, can you please look into this? It seems like this is legitimately a bug or a huge security flaw.

@afettouhi, it's really starting to look like you have other issues with your installation.

That may be but I don't know how to fix this or where to start. My installation is about 4 years old now but it is stock stable Arch.

[afettouhi]

But I never had issues with any of the prior versions of Proton btw.

[gardotd426]

@affettouhi, try reinstalling both the Soldier Runtime and Proton 5.13.

[gardotd426]

I would try with just Proton 5.13 first, right-click, uninstall, then try to launch a game with 5.13 selected, it will reinstall it.

If that doesn't work, then try reinstalling the runtime.

[oblitum]

Fixed it on my side.

• close steam
• uninstall steam-native-runtime (uninstalled recursively, which also removed steam, since I only used steam-native since I can't remember when)
• start steam
• removed all proton versions
• removed all Steam Linux Runtime - Soldier versions
• If removing those items from inside steam fail for any spurious issues (most probably it will), close steam, and remove each one that failed, manually (rm -rf the app directory and the appmanifest).
• start steam (clean with no native runtime nor any proton or soldier)
• launched Batman Arkham Knight. It installed Proton 5.13 automatically, but fails to load the game.
• launched Batman Arkham Knight, again. It installed the Soldier thing this time, automatically. Game loads.

[afettouhi]

Fixed it on my side.

* close steam

* uninstall steam-native-runtime (uninstalled recursively, which also removed steam, since I only used steam-native since I can't remember when)

* start steam

* removed all proton versions

* removed all Steam Linux Runtime - Soldier versions

* If removing those items from inside steam fail for any spurious issues (most probably it will), close steam, and remove each one that failed, manually (`rm -rf` the app directory and the appmanifest).

* start steam (clean with no native runtime nor any proton or soldier)

* launched Batman Arkham Knight. It installed Proton 5.13 automatically, but fails to load the game.

* launched Batman Arkham Knight, again. It installed the Soldier thing this time, automatically. Game loads.

I just tried that with Torchlight and removed all Proton versions and Steam Linux Runtime - Soldier versions. Closed Steam and reinstalled Torchlight and holy crap it launches now with proton 5.13.

[oblitum]

Okay, now replicating where issues lies:

1- I have a bunch of disks where games (& "tools") are spread.

First, heck, I don't know why, but damn steam client never respects my current library default install directory for Proton, and now this Soldier thing (not even a tool?).

Okay, until now I fixed that by moving the Proton install folder to a specific library where I want all these Protons installed only once, all in the same media. This always worked and I had the Protons all in my fastest disk. I either moved the installation to fix that (through steam), or I installed the Proton version myself instead of letting some game to install it automatically along side the game's library location.

I tried to move this Soldier thing and the Proton to my "tools" library location, now I'm back to square one. Seems like this thing can't be moved, I have no option but let it install alongside the game library or something, otherwise it gets broken.

Moving them back won't fix either. Only fix seems to clean up as before and let it install from game.

[oblitum]

Will have to have Protons/Soldier spread throughout game disks at random???? Sigh!

[oblitum]

It seems it's only for Steam Linux Runtime - Soldier for which I can't set the install location (it has to be beside the game that first requires it, so I'd have to have the game itself on the right disk for that if I really wished).

Cleaning up everything again. I do can install the Proton versions from Steam (manually, prior to launching any game), to the library location I wish. Then when I start some random game, like Batman, Steam will actually hang to install Steam Linux Runtime - Soldier, which will not go to the default library, it will go to the library the game is in, and the game will launch fine using the Proton already installed manually.

FWIW, I suspect I started the game fine after the Proton update on steam-native before all this mess, which I think started when I moved the Steam Linux Runtime - Soldier folder.

[DanMan]

Please just edit your posts, people, if yours is still the most recent. You trigger an alert for every subscriber of the thread with each new reply.

[Valmar33]

@gardotd426

But if you really want to know, when you install the steam-native-runtime package (which you're not supposed to do), it disables the bundled Steam runtime. If you go into Steam, and then click "Help" -> "System Information" and then scroll down to the "Steam Runtime" bit, it'll say "runtime disabled."

On Arch, Steam Runtime is only disable if you run steam-native. With steam, it runs as intended.

[TheDunkShot]

Well until proton 5.13-1 works for me (Thank to everyone who is trying to figure this out. I've done almost everything people are saying here and nothing works. Also I'm kinda suspicious that the people who get it to run are on amd and the people who can't run it are on nvidia.), COD: IW works with GloriousEggroll's newest custom proton.

[gardotd426]

Also I'm kinda suspicious that the people who get it to run are on amd and the people who can't run it are on nvidia.

Not even a little true.

https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-710535055

Look at the driver I'm running in the MangoHud overlay. RTX 3090. 5.13 works perfectly fine for me on Nvidia.

[TheDunkShot]

Also I'm kinda suspicious that the people who get it to run are on amd and the people who can't run it are on nvidia.

Not even a little true.

#4278 (comment)

Look at the driver I'm running in the MangoHud overlay. RTX 3090. 5.13 works perfectly fine for me on Nvidia.

I said that because Proton 5.13-1 works on my laptop running AMD, same distrobution, same desktop environment as my main PC.

[gardotd426]

Unfortunately it's not as simple as all that, it seems.

Hopefully the folks at Valve figure this out, because most people seem to be running it fine, but there are definitely plenty of people that aren't able to run it, and even the ones that do, requiring them to run something like sudo sysctl kernel.unprivileged_userns_clone=1 is a bit sketch.

[afettouhi]

Is anyone else having issues with Proton 5.13 not ending processes when exiting games? I have tested a few games now with proton 5.13 and I notice that I have several copies of winedevices.exe etc. running and other related processes

[andrew-mcmahon]

User namespaces appear to be enabled in my custom .config file and I'm compiling the latest stable kernel from kernel.org.
I'm currently using 5.9.1.
I see the same line enabled in the config file for a regular Debian provided kernel too (5.8.0.3)
CONFIG_USER_NS=y

The output from the command above i.e. sudo sysctl -n kernel.unprivileged_userns_clone returns the following:
sysctl: cannot stat /proc/sys/kernel/unprivileged_userns_clone: No such file or directory

sudo sysctl -a | grep kernel.unpr
kernel.unprivileged_bpf_disabled = 0
kernel.unprivileged_userns_apparmor_policy = 1  

But I don't think that's the issue on my end.

---

I'm compiling mesa from source; I expect most of you aren't so it might be a different problem.

I can play _any game_ if I do:

unset VK_ICD_FILENAMES  
steam

I _can't play anything_ if that variable is set to where my custom mesa drivers reside:

echo $VK_ICD_FILENAMES 
/opt/mesa/share/vulkan/icd.d/radeon_icd.i686.json:/opt/mesa/share/vulkan/icd.d/radeon_icd.x86_64.json

It stands to reason that any game can't work through DXVK if the Vulkan driver isn't working.
SUCCESS_steam-570940.log
FAIL_steam-570940.log

warn:  OpenVR: Failed to initialize OpenVR
info:  Enabled instance extensions:
info:    VK_KHR_get_surface_capabilities2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_0
info:  D3D11CoreCreateDevice: Using feature level D3D_FEATURE_LEVEL_11_0
info:  Device properties:
info:    Device name:     : AMD RADV TONGA (LLVM 10.0.1)
info:    Driver version   : 20.1.9
info:  Enabled device extensions:
info:    VK_AMD_memory_overallocation_behavior
info:    VK_AMD_shader_fragment_mask
info:    VK_EXT_depth_clip_enable
info:    VK_EXT_host_query_reset
info:    VK_EXT_memory_priority
info:    VK_EXT_robustness2
info:    VK_EXT_shader_stencil_export
info:    VK_EXT_shader_viewport_index_layer
info:    VK_EXT_transform_feedback
info:    VK_EXT_vertex_attribute_divisor
info:    VK_KHR_create_renderpass2
info:    VK_KHR_depth_stencil_resolve
info:    VK_KHR_draw_indirect_count
info:    VK_KHR_driver_properties
info:    VK_KHR_image_format_list
info:    VK_KHR_sampler_mirror_clamp_to_edge
info:    VK_KHR_swapchain

vs

warn:  OpenVR: Failed to initialize OpenVR
info:  Required Vulkan extension VK_KHR_surface not supported

radeon_icd.i686.json.txt
radeon_icd.x86_64.json.txt

Strange problem - never seen this before - I've been using Proton for ages now.

[GrieverV]

Apparently disabling SLR doesn't actually disable SLR with 5.13 so I had to forcefully disable it as shown here:
https://github.com/flightlessmango/MangoHud/issues/369#issuecomment-709902078

We shouldn't need to disable SLR/run with native so there's definitely something wrong.

Basic system information

Computer Information:
Manufacturer: Unknown
Model: Unknown
Form Factor: Desktop
No Touch Input Detected

Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 7 2700X Eight-Core Processor
CPU Family: 0x17
CPU Model: 0x8
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 4084 Mhz
16 logical processors
8 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Unsupported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported

Operating System Version:
"Arch Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 5.8.15-lqx1-1-lqx
X Server Vendor: The X.Org Foundation
X Server Release: 12009000
X Window Manager: GNOME Shell/Wayland
Steam Runtime Version:

Video Card:
Driver: AMD AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.38.0, 5.8.15-lqx1-1-lqx, LLVM 12.0.0)
Driver Version: 4.6 (Compatibility Profile) Mesa 20.3.0-devel (git-19aaafd4a6)
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x1002
DeviceID: 0x67df
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 1360 x 768
Desktop Resolution: 1360 x 768
Primary Display Size: 25.20" x 14.17" (28.90" diag)
64.0cm x 36.0cm (73.4cm diag)
Primary VRAM: 8192 MB

Sound card:
Audio device: CMI8786

Memory:
RAM: 16024 Mb

VR Hardware:
VR Headset: None detected

Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 127991 Mb
Largest Free Hard Disk Block: 22340 Mb

[kisak-valve]

Hello @GrieverV, looks like #4270 applies to your system.

[gustavolinux]

Well. It's working fine here(Arch Linux/5700XT/New Kernel) and finally GRID 2019 is running very well. All the fps drops were gone.

[CSahajdacny]

On my Ubuntu 20.04.1 machine, NO game works via Proton 5.13..
Previous Proton versions works.
Even the Proton Logs are not created if I use Proton 5.13...

[oblitum]

@CSahajdacny tried https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-710737373?

[asdf-qwert]

Managed to get the proton log for Deep Rock Galactic with Proton 5.13 (works correctly with 5.0)
https://gist.github.com/asdf-qwert/7860566e4169efb64bcc28cafbe97301#file-proton5-13

[DMGPage]

Just for the record, I have same issue. Not even one game was working with proton 5.13. And what is more interesting, it removes some files after using it. I tested on Assassin's Creed Odyssey and after using proton 5.13, Uplay was missing and I could not launch it with proton 5.0. After deleting and installing Assassin's Creed Odyssey with proton 5.13, game started to work. But same thing with Conan Exiles do not work. Even after reinstalling game crashes on loading saves.

[Shished]

Nothing works when I'm trying to launch any game with proton 5.13 with native Steam on Arch,
Terminal shows this errors:

/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new

[cerealbox]

i am also experiencing the same problem.
a recently installed and fully updated version of arch linux launching a game with proton 5.13-1 does nothing and i receive several errors like this:

/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so

[gardotd426]

COD: IW works with GloriousEggroll's newest custom proton.

I can't get it to launch with anything other than 5.13, 5.9-GE-ST-8 fails.

[jaubin]

Could not reproduce the issues on Debian Stable / KDE / Linux 4.19 / NVidia 450.66

[aaaaaaaaargh]

i am also experiencing the same problem.
a recently installed and fully updated version of arch linux launching a game with proton 5.13-1 does nothing and i receive several errors like this:

/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so

Same issue here running RDR2 using proton 5.13-1 on Manjaro 5.8.11-1 and NVIDIA 450.66. I think the issue is that the given symbol, g_task_new is not defined in glib2 (anymore?) which is required by libgvfscommon. I don't really understand why this is broken now but I think the issue might be in the gvfs build itself, because it clearly exports g_task_new as undefined (zero address):

readelf -Ws /usr/lib/gvfs/libgvfscommon.so | grep g_task_new
 24: 0000000000000000     0 FUNC    GLOBAL DEFAULT  UND g_task_new

So am I correct to assume this is a problem within the Arch packages?

EDIT: As time of writing, the versions of my local installation are gvsf 1.44.1-4 and glib2 2.66.0-1.

[ryester27]

Delete Proton 5.13 and Steam Linux Runtime - Soldier, then restart. Instead of reinstalling everything yourself through the tools section of the library, have the game install them for you when it launches. Might need to launch the game 2 or 3 times in order for both Proton and Soldier to be installed again.

Linux Runtime Soldier is also appearing as a game in the library for some reason

[afettouhi]

Since I made this bug report originally. I think I will give experience with Proton 5.13 after getting it to work. I got it working by reinstalling Proton 5.13 as the new Steam Runtime as suggested in this post here

https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-710737373

All the games that worked in previous versions of Proton work in 5.13 (at least the ones I tested). But Proton 5.13 breaks compatibility tools like steamtinkerlaunch etc. But one thing that I experience with every game I launch with Proton 5.13 are hanging wine processes even after games are closed. 3 processes remain every time, each game I launch, there are: rundll32.exe, wineserver & winedevice.exe. I have to kill these manually in order to close steam and sometimes I even have kill steam in order for it to close. Does anyone else experience this with 5.13 for those that have it working?

[oblitum]

@afettouhi I'm not experiencing that on ArchLinux, the processes are closing without issues. The only problem is when the game for some random reason hangs or crashes, then yeah, that may happen, because the game didn't close properly, but this is rare to happen, most of time it closes as expected and all the other sibling processes follow.

[gardotd426]

I also can't reproduce on Arch Linux (unless there is a crash, as was said)

On Sun, Oct 18, 2020 at 4:19 PM Francisco Lopes [e-mail]
wrote:

@afettouhi https://github.com/afettouhi I'm not experiencing that on
ArchLinux, the processes are closing without issues. The only problem is
when the game for some random reason hangs or crash, then yeah, that may
happen, because the game didn't close properly, but this is rare to happen,
most of time it closes as expected and all the other process follow.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-711416497,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y337WU37QUG6WC5YPSXTSLNEVPANCNFSM4STRMDRA
.

[the-black-wolf]

None of the advices help.
I am running on popOS 20.04 and Proton 5.13 is borked entirely. I can't even get a log of whats happening, it just dies immediately after launch on every game. Steam generates no log entries in terminal, proton_log generates no log file. When I switch to running game on Steam Linux Runtime the Steam just destroys the whole game and deletes all files in game folder, so running the game reports missing executable. Whats more bizarre is that Verify integrity reports that all files are valid ?!? And there are NO files. what in the world is happening here?

[aaaaaaaaargh]

Since I made this bug report originally. I think I will give experience with Proton 5.13 after getting it to work. I got it working by reinstalling Proton 5.13 as the new Steam Runtime as suggested in this post here

#4278 (comment)

All the games that worked in previous versions of Proton work in 5.13 (at least the ones I tested). But Proton 5.13 breaks compatibility tools like steamtinkerlaunch etc. But one thing that I experience with every game I launch with Proton 5.13 are hanging wine processes even after games are closed. 3 processes remain every time, each game I launch, there are: rundll32.exe, wineserver & winedevice.exe. I have to kill these manually in order to close steam and sometimes I even have kill steam in order for it to close. Does anyone else experience this with 5.13 for those that have it working?

Unfortunately for me this does not solve the problem. So what you are proposing basically is to reinstall everything in order to not rely on native libraries then, correct? If that is the case I am wondering why proton still seems to use libraries found in /usr/lib then. I did not install steam-native, just steam-manjaro. Any ideas on that?

[gardotd426]

None of the advices help.
I am running on popOS 20.04 and Proton 5.13 is borked entirely. I can't even get a log of whats happening, it just dies immediately after launch on every game. Steam generates no log entries in terminal, proton_log generates no log file. When I switch to running game on Steam Linux Runtime the Steam just destroys the whole game and deletes all files in game folder, so running the game reports missing executable. Whats more bizarre is that Verify integrity reports that all files are valid ?!? And there are NO files. what in the world is happening here?

What you're seeing when you choose "Steam Linux Runtime" from the drop-down (all the files "disappearing") is what's supposed to happen. The "Steam Linux Runtime" option in that menu is for NATIVE games, so you can't launch Windows games with it selected. The files aren't being deleted, they just aren't playable. Never select "Steam Linux Runtime" from the drop-down menu for Windows titles.

I suggest you retry the steps mentioned in this comment specifically, https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-710737373, since your issue sounds like Proton/the runtime was not installed correctly.

[gardotd426]

Unfortunately for me this does not solve the problem. So what you are proposing basically is to reinstall everything in order to not rely on native libraries then, correct?

It's not "in order to rely on the native libraries," it's "because Proton 5.13 literally depends on Steam Runtime Soldier to work, and cannot work without it."

[gardenappl]

Not sure if this is helpful to anybody but:

All my problems with Proton 5.13 went away as soon as I migrated it to a non-NTFS filesystem.

(it used to complain about symlinks, though it wasn't the same error as reported by others)

[the-black-wolf]

Not sure if this is helpful to anybody but:

All my problems with Proton 5.13 went away as soon as I migrated it to a non-NTFS filesystem.

I am on ext4

[the-black-wolf]

None of the advices help.
I am running on popOS 20.04 and Proton 5.13 is borked entirely. I can't even get a log of whats happening, it just dies immediately after launch on every game. Steam generates no log entries in terminal, proton_log generates no log file. When I switch to running game on Steam Linux Runtime the Steam just destroys the whole game and deletes all files in game folder, so running the game reports missing executable. Whats more bizarre is that Verify integrity reports that all files are valid ?!? And there are NO files. what in the world is happening here?

What you're seeing when you choose "Steam Linux Runtime" from the drop-down (all the files "disappearing") is what's supposed to happen. The "Steam Linux Runtime" option in that menu is for NATIVE games, so you can't launch Windows games with it selected. The files aren't being deleted, they just aren't playable. Never select "Steam Linux Runtime" from the drop-down menu for Windows titles.

I suggest you retry the steps mentioned in this comment specifically, #4278 (comment), since your issue sounds like Proton/the runtime was not installed correctly.

I did, it does not work. First, after downloading Proton it just says "Preparing to launch XYZ" and stays there forever. When I close that window and start it again, THEN it starts downlaoding Soldier, and once it downloads it it offers to play, but once game is started it exits immediately. Its like that first setup process is blocked and I kill it prematurely and after that its all borked.

The wrots thing is I can't even debug this, absolutely NO LOGS of any kind are being generated.

[gardotd426]

How did you do it? By deleting Proton and the Soldier runtime manually, or
by clicking "Uninstall" on both of them through Steam?

On Sun, Oct 18, 2020 at 5:25 PM Black Wolf [e-mail] wrote:

None of the advices help.
I am running on popOS 20.04 and Proton 5.13 is borked entirely. I can't
even get a log of whats happening, it just dies immediately after launch on
every game. Steam generates no log entries in terminal, proton_log
generates no log file. When I switch to running game on Steam Linux
Runtime the Steam just destroys the whole game and deletes all files in
game folder, so running the game reports missing executable. Whats more
bizarre is that Verify integrity reports that all files are valid ?!? And
there are NO files. what in the world is happening here?

What you're seeing when you choose "Steam Linux Runtime" from the
drop-down (all the files "disappearing") is what's supposed to happen. The
"Steam Linux Runtime" option in that menu is for NATIVE games, so you can't
launch Windows games with it selected. The files aren't being deleted, they
just aren't playable. Never select "Steam Linux Runtime" from the drop-down
menu for Windows titles.

I suggest you retry the steps mentioned in this comment specifically, #4278
(comment)
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-710737373,
since your issue sounds like Proton/the runtime was not installed correctly.

I did, it does not work. First, after downloading Proton it just says
"Preparing to launch XYZ" and stays there forever. When I close that window
and start it again, THEN it starts downlaoding Soldier, and once it
downloads it it offers to play, but once game is started it exits
immediately. Its like that first setup process is blocked and I kill it
prematurely and after that its all borked.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-711425963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y337HIMDCSURXQ22D6SDSLNMNDANCNFSM4STRMDRA
.

[aaaaaaaaargh]

Unfortunately for me this does not solve the problem. So what you are proposing basically is to reinstall everything in order to not rely on native libraries then, correct?

It's not "in order to rely on the native libraries," it's "because Proton 5.13 literally depends on Steam Runtime Soldier to work, and cannot work without it."

Thanks for clarifying, I never saw this native runtime soldier dependency before, so I don't know too much about whether it was important here. However, how does the proposed steps help in solving this issue? As far as I can tell this seems to be an incompatibility between gvfs and glib, is it not?

EDIT: By the way, if that helps, I tried to clean my installation in any way I could think of, also by manually deleting the files in .local/share/Steam as well as .steam plus uninstalling all of pacmans steam-related packages (in my case only steam-manjaro).

[the-black-wolf]

How did you do it? By deleting Proton and the Soldier runtime manually, or by clicking "Uninstall" on both of them through Steam?

I tried it both ways (when manually deleting I also removed manifests), it didn't help.

[the-black-wolf]

Ok, at least it started producing logs finally

Expand for log...

GameAction [AppID 1283190, ActionID 1] : LaunchApp changed task to ProcessingInstallScript with ""
_v2-entry-point[48211]: STEAM_COMPAT_APP_ID=1283190
_v2-entry-point[48211]: STEAM_COMPAT_SESSION_ID=c2cd233a403c1b0a
_v2-entry-point[48211]: XDG_RUNTIME_DIR=/run/user/1000
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
x86_64-linux-gnu-capsule-capture-libs: code 2: Missing dependencies: Could not find "libnvidia-fatbinaryloader.so.440.100" in LD_LIBRARY_PATH "", ld.so.cache, /lib or /usr/lib
pressure-vessel-wrap[48229]: Child process exited with code 1
ln: failed to create symbolic link '/run/user/1000/SteamLinuxRuntime.c2cd233a403c1b0a/socket' -> '': No such file or directory
_v2-entry-point[48246]: STEAM_COMPAT_APP_ID=1283190
_v2-entry-point[48246]: STEAM_COMPAT_SESSION_ID=c2cd233a403c1b0a
_v2-entry-point[48246]: XDG_RUNTIME_DIR=/run/user/1000
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
x86_64-linux-gnu-capsule-capture-libs: code 2: Missing dependencies: Could not find "libnvidia-fatbinaryloader.so.440.100" in LD_LIBRARY_PATH "", ld.so.cache, /lib or /usr/lib
pressure-vessel-wrap[48258]: Child process exited with code 1
ln: failed to create symbolic link '/run/user/1000/SteamLinuxRuntime.c2cd233a403c1b0a/socket' -> '': No such file or directory
_v2-entry-point[48275]: STEAM_COMPAT_APP_ID=1283190
_v2-entry-point[48275]: STEAM_COMPAT_SESSION_ID=c2cd233a403c1b0a
_v2-entry-point[48275]: XDG_RUNTIME_DIR=/run/user/1000
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
x86_64-linux-gnu-capsule-capture-libs: code 2: Missing dependencies: Could not find "libnvidia-fatbinaryloader.so.440.100" in LD_LIBRARY_PATH "", ld.so.cache, /lib or /usr/lib
pressure-vessel-wrap[48287]: Child process exited with code 1
ln: failed to create symbolic link '/run/user/1000/SteamLinuxRuntime.c2cd233a403c1b0a/socket' -> '': No such file or directory
_v2-entry-point[48304]: STEAM_COMPAT_APP_ID=1283190
_v2-entry-point[48304]: STEAM_COMPAT_SESSION_ID=c2cd233a403c1b0a
_v2-entry-point[48304]: XDG_RUNTIME_DIR=/run/user/1000
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
x86_64-linux-gnu-capsule-capture-libs: code 2: Missing dependencies: Could not find "libnvidia-fatbinaryloader.so.440.100" in LD_LIBRARY_PATH "", ld.so.cache, /lib or /usr/lib
pressure-vessel-wrap[48316]: Child process exited with code 1
ln: failed to create symbolic link '/run/user/1000/SteamLinuxRuntime.c2cd233a403c1b0a/socket' -> '': No such file or directory
/data/src/clientdll/installscript_posix.cpp (419) : Assertion Failed: Standalone evaluator returned error code for app 1283190
/data/src/clientdll/installscript_posix.cpp (419) : Assertion Failed: Standalone evaluator returned error code for app 1283190
Installing breakpad exception handler for appid(steam)/version(1602795778)
crash_20201018234035_42.dmp[48337]: Uploading dump (out-of-process)
/tmp/dumps/crash_20201018234035_42.dmp
GameAction [AppID 1283190, ActionID 1] : LaunchApp changed task to SynchronizingCloud with ""
GameAction [AppID 1283190, ActionID 1] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 1283190, ActionID 1] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 1283190, ActionID 1] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 1283190, ActionID 1] : LaunchApp continues with user response "CreatingProcess"
Opted-in Controller Mask for AppId 1283190: 0
Game update: AppID 1283190 "", ProcID 48338, IP 0.0.0.0:0
Starting app 1283190
>>> Adding process 48338 for game ID 1283190
GameAction [AppID 1283190, ActionID 1] : LaunchApp changed task to WaitingGameWindow with ""
ERROR: ld.so: object '/home/mmix/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/mmix/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/mmix/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pid 48342 != 48340, skipping destruction (fork without exec?)
GameAction [AppID 1283190, ActionID 1] : LaunchApp changed task to Completed with ""
>>> Adding process 48339 for game ID 1283190
ERROR: ld.so: object '/home/mmix/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 48340 for game ID 1283190
_v2-entry-point[48340]: STEAM_COMPAT_APP_ID=1283190
_v2-entry-point[48340]: STEAM_COMPAT_SESSION_ID=c2cd233a403c1b0a
_v2-entry-point[48340]: XDG_RUNTIME_DIR=/run/user/1000
ERROR: ld.so: object '/home/mmix/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
>>> Adding process 48341 for game ID 1283190
>>> Adding process 48343 for game ID 1283190
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
ERROR: ld.so: object '/home/mmix/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 48344 for game ID 1283190
>>> Adding process 48345 for game ID 1283190
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
>>> Adding process 48346 for game ID 1283190
x86_64-linux-gnu-capsule-capture-libs: code 2: Missing dependencies: Could not find "libnvidia-fatbinaryloader.so.440.100" in LD_LIBRARY_PATH "", ld.so.cache, /lib or /usr/lib
pressure-vessel-wrap[48352]: Child process exited with code 1
ln: failed to create symbolic link '/run/user/1000/SteamLinuxRuntime.c2cd233a403c1b0a/socket' -> '': No such file or directory
ERROR: ld.so: object '/home/mmix/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
ERROR: ld.so: object '/home/mmix/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_get_source_tag
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_task_data
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
pressure-vessel-launch[48369]: Can't connect to peer socket: Could not connect: No such file or directory
>>> Adding process 48368 for game ID 1283190
>>> Adding process 48369 for game ID 1283190
Game removed: AppID 1283190 "", ProcID 48338 
Uploaded AppInterfaceStats to Steam
Exiting app 1283190
No cached sticky mapping in ActivateActionSet.crash_20201018234035_42.dmp[48337]: Finished uploading minidump (out-of-process): success = yes
crash_20201018234035_42.dmp[48337]: response: CrashID=bp-f42e0d31-049b-4b96-8401-346572201018
crash_20201018234035_42.dmp[48337]: file ''/tmp/dumps/crash_20201018234035_42.dmp'', upload yes: ''CrashID=bp-f42e0d31-049b-4b96-8401-346572201018''

[kisak-valve]

Hello @the-black-wolf, x86_64-linux-gnu-capsule-capture-libs: code 2: Missing dependencies: Could not find "libnvidia-fatbinaryloader.so.440.100" in LD_LIBRARY_PATH "", ld.so.cache, /lib or /usr/lib sounds like the line of interest from your log. We've heard similar before at https://github.com/ValveSoftware/steam-runtime/issues/275.

[the-black-wolf]

@kisak-valve well, this is getting weirder then. Why would it want to look for 440.100? I have 455.28 installed. and I purged all before installing it.
I have no libnvidia-fatbinaryloader* files on my / tree.

[gardotd426]

Read the comments over at the post kisak linked. Dude there doesn't even
have an Nvidia GPU. But read it carefully, he had some old files I guess
from a previous Nvidia installation.

On Sun, Oct 18, 2020 at 6:02 PM Black Wolf [e-mail] wrote:

@kisak-valve https://github.com/kisak-valve well, this is getting
weirder then. Why would it want to look for 440.100? I have 455.28
installed. and I purged all before installing it.
I have no libnvidia-fatbinaryloader* files on my / tree.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-711430020,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y336OYHY3FHKE3622VU3SLNQXVANCNFSM4STRMDRA
.

[the-black-wolf]

@gardotd426 I did, I had two files

-rw-r--r--  1 root root 1491816 Jun  1 11:10 libnvidia-gtk2.so.440.82
-rw-r--r--  1 root root 1500488 Jun  1 11:10 libnvidia-gtk3.so.440.82

I moved them, but nothing changed. So I placed them back because nvidia-settings depends on them.

[the-black-wolf]

oh, for f sake. popos installed 440 parallel to my 455 :( one sec to clean things up

[aaaaaaaaargh]

I am just curious: How come nobody mentions the loads of unresolved symbol errors in your log? Are these completely unrelated?

[gardotd426]

Make sure you only have ONE driver version installed, no parallels, none of
that mess, just either 450 or 455 (or I guess 440), and try again.

On Sun, Oct 18, 2020 at 6:11 PM Black Wolf [e-mail] wrote:

oh, for f sake. popos installed 440 parallel to my 455 :( one sec to clean
things up

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-711431036,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y334QQJ4MEGWQTQAABW3SLNRZ5ANCNFSM4STRMDRA
.

[DeX77]

Managed to at least start some games again with removing all proton and the soldier thing.
Now I get:

libGL error: MESA-LOADER: failed to open radeonsi (search paths /overrides/lib/x86_64-linux-gnu/dri:/overrides/lib/i386-linux-gnu/dri)

(With Proton 5.13. With Proton 5.0-9 not)

[the-black-wolf]

@gardotd426 @kisak-valve I just purged all nvidia* and reinstalled only nvidia-driver-455:

mmix@BlackWolf:~$ sudo apt list nvidia* --installed
[sudo] password for mmix: 
Listing... Done
nvidia-compute-utils-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed,automatic]
nvidia-dkms-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed,automatic]
nvidia-driver-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed]
nvidia-kernel-common-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed,automatic]
nvidia-kernel-source-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed,automatic]
nvidia-settings/focal-updates,now 440.82-0ubuntu0.20.04.1 amd64 [installed,automatic]
nvidia-utils-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed,automatic]
mmix@BlackWolf:~$ nvidia-smi
Mon Oct 19 00:48:25 2020       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 455.28       Driver Version: 455.28       CUDA Version: 11.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce RTX 2080    Off  | 00000000:01:00.0  On |                  N/A |
| 30%   34C    P8     7W / 245W |   1586MiB /  7979MiB |      1%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
...                                                                               

However, in the log file, it still wants to load libnvidia-fatbinaryloader.so.440.100.

[gardotd426]

You might also have to uninstall/reinstall Proton 5.13 and the Soldier
runtime.

On Sun, Oct 18, 2020 at 6:55 PM Black Wolf [e-mail] wrote:

@gardotd426 https://github.com/gardotd426 @kisak-valve
https://github.com/kisak-valve I just purged all nvidia* and
reinstalled only nvidia-driver-455:

mmix@BlackWolf:~$ sudo apt list nvidia* --installed
[sudo] password for mmix:
Listing... Done
nvidia-compute-utils-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed,automatic]
nvidia-dkms-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed,automatic]
nvidia-driver-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed]
nvidia-kernel-common-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed,automatic]
nvidia-kernel-source-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed,automatic]
nvidia-settings/focal-updates,now 440.82-0ubuntu0.20.04.1 amd64 [installed,automatic]
nvidia-utils-455/focal,now 455.28-0pop1~1602094814~20.04~9eb7df9 amd64 [installed,automatic]
mmix@BlackWolf:~$ nvidia-smi
Mon Oct 19 00:48:25 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 455.28 Driver Version: 455.28 CUDA Version: 11.1 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 GeForce RTX 2080 Off | 00000000:01:00.0 On | N/A |
| 30% 34C P8 7W / 245W | 1586MiB / 7979MiB | 1% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
...

However, in the log file, it still wants to load
libnvidia-fatbinaryloader.so.440.100.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-711436326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y33ZED5ZHVJJET7JC22TSLNW6FANCNFSM4STRMDRA
.

[the-black-wolf]

Did that as well (sorry didnt mention).
Its really weird, Its like soldier has a hard dependency on 440 driver?

[the-black-wolf]

ok, seems popos has been playing with packages, I did not have two drivers, 440 is just a transitional for 455. I'll try now to force the 440.100 driver from ubuntu

```
mmix@BlackWolf:~$ sudo apt info nvidia-driver-440 -a
Package: nvidia-driver-440
Version: 455.28-0pop1~1602094814~20.04~9eb7df9
Priority: optional
Section: libs
Source: nvidia-graphics-drivers-455
Maintainer: Ubuntu Core Developers [e-mail]
Installed-Size: 18.4 kB
Depends: nvidia-driver-455
Download-Size: 5,532 B
APT-Manual-Installed: yes
APT-Sources: http://ppa.launchpad.net/system76/pop/ubuntu focal/main amd64 Packages
Description: Transitional package for nvidia-driver-455
This is a transitional package for nvidia-driver-455, and can be safely removed after the installation is complete.
````

[the-black-wolf]

And I hit the wall. There are unmet dependencies for 440.100 :( I guess Proton 5.13 is a no show for PopOS. I still do not understand why Soldier demands a specific version of the driver. why not just use the latest available?

mmix@BlackWolf:~$ sudo apt install nvidia-driver-440=440.82+really.440.64-0ubuntu6
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nvidia-driver-440 : Depends: libnvidia-gl-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Depends: nvidia-dkms-440 (= 440.82+really.440.64-0ubuntu6) or
                              nvidia-dkms-440 (= 440.82+really.440.64-0ubuntu4)
                     Depends: nvidia-kernel-source-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Depends: libnvidia-compute-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Depends: libnvidia-extra-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Depends: nvidia-compute-utils-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Depends: libnvidia-decode-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Depends: libnvidia-encode-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Depends: nvidia-utils-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Depends: xserver-xorg-video-nvidia-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Depends: libnvidia-cfg1-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Depends: libnvidia-ifr1-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Depends: libnvidia-fbc1-440 (= 440.82+really.440.64-0ubuntu6) but 455.28-0pop1~1602094814~20.04~9eb7df9 is to be installed
                     Recommends: nvidia-settings but it is not going to be installed
                     Recommends: nvidia-prime (>= 0.8)
                     Recommends: libnvidia-compute-440:i386 (= 440.82+really.440.64-0ubuntu6)
                     Recommends: libnvidia-decode-440:i386 (= 440.82+really.440.64-0ubuntu6)
                     Recommends: libnvidia-encode-440:i386 (= 440.82+really.440.64-0ubuntu6)
                     Recommends: libnvidia-ifr1-440:i386 (= 440.82+really.440.64-0ubuntu6)
                     Recommends: libnvidia-fbc1-440:i386 (= 440.82+really.440.64-0ubuntu6)
                     Recommends: libnvidia-gl-440:i386 (= 440.82+really.440.64-0ubuntu6)
E: Unable to correct problems, you have held broken packages.

[gardotd426]

It's not that, man. Steam isn't going to require different versions of the Nvidia driver for different distros. If your assumption was correct no one on Nvidia and a driver other than 440.100 would be able to use Proton 5.13, and that's not remotely true. I'm on 455.28 and it works fine (from the beginning), and others on Nvidia are running it fine as well.

[kisak-valve]

@the-black-wolf, I don't fully understand what's involved here, but what we do know is that libnvidia-fatbinaryloader is part of nvidia's CUDA/OpenCL driver stack.

I'm fairly sure that pressure-vessel is walking through the host system for additional dependencies that are needed to forward into the container environment and there's something leftover from when 440.100 was installed in the past. It's not that pressure-vessel requires a specific driver version, it's just that there's a new edge case that hasn't been seen before and pressure-vessel hasn't been taught how to handle it yet.

[gardotd426]

If you're on flash storage, I would honestly run sudo find /usr/ | grep 440.100 and see if there are any results. If not, maybe check a couple other directories in the root directory where there might be some 440.100 files left. Hell even if your root partition isn't on flash, I still would do it.

[makitsune]

I'm having problems with Proton 5.13 as well. Can't run any Unity games which are usually very stable.

Arch Linux, nvidia 455.28-7, linux 5.8.14.arch1-1. I downgraded from newest Linux 5.9 since there are some issues with the Nvidia driver. https://www.reddit.com/r/archlinux/comments/jd1qu1/proprietary_nvidia_driver_not_supported_for/

[the-black-wolf]

@kisak-valve, @gardotd426
ok, yes, finally. You were both right, there were bunch of leftover libs not cleaned up properly from 440.100

List

mmix@BlackWolf:~$ sudo find /usr/ | grep 440.100
/usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.440.100
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.440.100
/usr/lib/x86_64-linux-gnu/libnvidia-cbl.so.440.100
/usr/lib/x86_64-linux-gnu/libnvidia-eglcore.so.440.100
/usr/lib/x86_64-linux-gnu/libnvidia-glvkspirv.so.440.100
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.100
/usr/lib/x86_64-linux-gnu/libnvidia-glsi.so.440.100
/usr/lib/x86_64-linux-gnu/libGLESv1_CM_nvidia.so.440.100
/usr/lib/x86_64-linux-gnu/nvidia/xorg/libglxserver_nvidia.so.440.100
/usr/lib/x86_64-linux-gnu/libnvoptix.so.440.100
/usr/lib/x86_64-linux-gnu/libnvidia-rtcore.so.440.100
/usr/lib/x86_64-linux-gnu/libGLESv2_nvidia.so.440.100
/usr/lib/x86_64-linux-gnu/libnvidia-tls.so.440.100
/usr/lib/i386-linux-gnu/libEGL_nvidia.so.440.100
/usr/lib/i386-linux-gnu/libGLX_nvidia.so.440.100
/usr/lib/i386-linux-gnu/libnvidia-eglcore.so.440.100
/usr/lib/i386-linux-gnu/libnvidia-glvkspirv.so.440.100
/usr/lib/i386-linux-gnu/libnvidia-glcore.so.440.100
/usr/lib/i386-linux-gnu/libnvidia-glsi.so.440.100
/usr/lib/i386-linux-gnu/libGLESv1_CM_nvidia.so.440.100
/usr/lib/i386-linux-gnu/libGLESv2_nvidia.so.440.100
/usr/lib/i386-linux-gnu/libnvidia-tls.so.440.100

I fed this to rm, restarted Steam and now the games work in 5.13. I didnt even have to reinstall proton/soldier.
What a silly issue.

NOTE: before removing files found with find/grep, its advisable to first check if there are packages who own them and remove packages instead.

[gardotd426]

Those issues don't affect gaming, and can be fixed rather easily by using
TK-Glitch's nvidia-all https://github.com/frogging-family/nvidia-all (patch
is automatically included for 5.9)

On Sun, Oct 18, 2020 at 7:47 PM Maki [e-mail] wrote:

I'm having problems with Proton 5.13 as well. Can't run any Unity games
which are usually very stable.

Arch Linux, nvidia 455.28-7, linux 5.8.14.arch1-1. I downgraded from
newest Linux 5.9 since there are some issues with the Nvidia driver.
https://www.reddit.com/r/archlinux/comments/jd1qu1/proprietary_nvidia_driver_not_supported_for/

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-711442195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y333NLH77DYEZYRKPDPLSLN475ANCNFSM4STRMDRA
.

[gardotd426]

This is one reason why I don't use *Buntus, because of the transitional
packages that can often create messes like this. Anyway, glad you got it
working

On Sun, Oct 18, 2020 at 7:55 PM Black Wolf [e-mail] wrote:

@kisak-valve https://github.com/kisak-valve, @gardotd426
https://github.com/gardotd426
ok, yes, finally. You were both right, there were bunch of leftover libs
not cleaned up properly from 440.100
List

mmix@BlackWolf:~$ sudo find /usr/ | grep 440.100 /usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.440.100 /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.440.100 /usr/lib/x86_64-linux-gnu/libnvidia-cbl.so.440.100 /usr/lib/x86_64-linux-gnu/libnvidia-eglcore.so.440.100 /usr/lib/x86_64-linux-gnu/libnvidia-glvkspirv.so.440.100 /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.100 /usr/lib/x86_64-linux-gnu/libnvidia-glsi.so.440.100 /usr/lib/x86_64-linux-gnu/libGLESv1_CM_nvidia.so.440.100 /usr/lib/x86_64-linux-gnu/nvidia/xorg/libglxserver_nvidia.so.440.100 /usr/lib/x86_64-linux-gnu/libnvoptix.so.440.100 /usr/lib/x86_64-linux-gnu/libnvidia-rtcore.so.440.100 /usr/lib/x86_64-linux-gnu/libGLESv2_nvidia.so.440.100 /usr/lib/x86_64-linux-gnu/libnvidia-tls.so.440.100 /usr/lib/i386-linux-gnu/libEGL_nvidia.so.440.100 /usr/lib/i386-linux-gnu/libGLX_nvidia.so.440.100 /usr/lib/i386-linux-gnu/libnvidia-eglcore.so.440.100 /usr/lib/i386-linux-gnu/libnvidia-glvkspirv.so.440.100 /usr/lib/i386-linux-gnu/libnvidia-glcore.so.440.100 /usr/lib/i386-linux-gnu/libnvidia-glsi.so.440.100 /usr/lib/i386-linux-gnu/libGLESv1_CM_nvidia.so.440.100 /usr/lib/i386-linux-gnu/libGLESv2_nvidia.so.440.100 /usr/lib/i386-linux-gnu/libnvidia-tls.so.440.100

I fed this to rm, restarted Steam and now the games work in 5.13. I didnt
even have to reinstall proton/soldier.
What a silly issue.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-711443063,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y334KYKHDOH2YDQG3M6LSLN55TANCNFSM4STRMDRA
.

[kisak-valve]

@the-black-wolf, glad to hear you got past the snafu. Can you add a note to your comment encouraging anyone who comes across the same situation to check if any package owns the files before deleting them? It's too late for you since they're already gone.

[the-black-wolf]

@the-black-wolf, glad to hear you got past the snafu. Can you add a note to your comment encouraging anyone who comes across the same situation to check if any package owns the files before deleting them? It's too late for you since they're already gone.

Sure. Though its not late for me either, I first cp --parent them, I'll restore them tomorrow and try to track down owners, if any.

Actually, I ran it form the backup, using folder structure dumped in a file. None of the files belonged to any package:

Package test

mmix@BlackWolf:~/dddd$ dpkg -S `cat list.txt`
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libnvidia-cbl.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libnvidia-eglcore.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libnvidia-glvkspirv.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libnvidia-glsi.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libGLESv1_CM_nvidia.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/nvidia/xorg/libglxserver_nvidia.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libnvoptix.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libnvidia-rtcore.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libGLESv2_nvidia.so.440.100
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libnvidia-tls.so.440.100
dpkg-query: no path found matching pattern /usr/lib/i386-linux-gnu/libEGL_nvidia.so.440.100
dpkg-query: no path found matching pattern /usr/lib/i386-linux-gnu/libGLX_nvidia.so.440.100
dpkg-query: no path found matching pattern /usr/lib/i386-linux-gnu/libnvidia-eglcore.so.440.100
dpkg-query: no path found matching pattern /usr/lib/i386-linux-gnu/libnvidia-glvkspirv.so.440.100
dpkg-query: no path found matching pattern /usr/lib/i386-linux-gnu/libnvidia-glcore.so.440.100
dpkg-query: no path found matching pattern /usr/lib/i386-linux-gnu/libnvidia-glsi.so.440.100
dpkg-query: no path found matching pattern /usr/lib/i386-linux-gnu/libGLESv1_CM_nvidia.so.440.100
dpkg-query: no path found matching pattern /usr/lib/i386-linux-gnu/libGLESv2_nvidia.so.440.100
dpkg-query: no path found matching pattern /usr/lib/i386-linux-gnu/libnvidia-tls.so.440.100

[afettouhi]

Since I made this bug report originally. I think I will give experience with Proton 5.13 after getting it to work. I got it working by reinstalling Proton 5.13 as the new Steam Runtime as suggested in this post here
#4278 (comment)
All the games that worked in previous versions of Proton work in 5.13 (at least the ones I tested). But Proton 5.13 breaks compatibility tools like steamtinkerlaunch etc. But one thing that I experience with every game I launch with Proton 5.13 are hanging wine processes even after games are closed. 3 processes remain every time, each game I launch, there are: rundll32.exe, wineserver & winedevice.exe. I have to kill these manually in order to close steam and sometimes I even have kill steam in order for it to close. Does anyone else experience this with 5.13 for those that have it working?

Unfortunately for me this does not solve the problem. So what you are proposing basically is to reinstall everything in order to not rely on native libraries then, correct? If that is the case I am wondering why proton still seems to use libraries found in /usr/lib then. I did not install steam-native, just steam-manjaro. Any ideas on that?

I am not proposing anything. I am just stating what I did in order to get Proton 5.13 working.

[afettouhi]

Here is the Proton log from running Doom Eternal with 5.13
steam-782330.log

[BdMdesigN]

I have the same problem. With Proton 5.13 no Game starts.

I'm on openSUSE Tumbleweed. deinstalling and reinstall from Proton 5.13-1 has no effect. Same with the Steam Linux Runtime - Soldier. Logs are not created.

I try the stable and the Beta Steam 4 Linux Client. The result is the same.

Here my Systeminfos: https://gist.github.com/BdMdesigN/c6989e396003be22022a9a5642d63444

[aaaaaaaaargh]

I am still concerned with the unresolved symbols in recent Arch installations and really don't understand why nobody else seems to be bothered by those. As far as I can tell from the information shared here and my own observations this is very likely to be causing this (maybe amongst other things). However, please feel free to prove me wrong, because otherwise I would still recommend to investigate this further.

[DeX77]

I am still concerned with the unresolved symbols in recent Arch installations and really don't understand why nobody else seems to be bothered by those. As far as I can tell from the information shared here and my own observations this is very likely to be causing this (maybe amongst other things). However, please feel free to prove me wrong, because otherwise I would still recommend to investigate this further.

You might be right, that those missing symbols are part of the problem. But:
a) those errors appear even on *untu based systems
b) I can asure you everything needing gvfs on host just works fine

So those missing symbols are more of a symptom of a deeper problem, not the reason for the problems

[smcv]

/usr/lib/gvfs/libgvfscommon.so: undefined symbol: g_task_new

This looks bad but is actually harmless, and can be ignored. It happens because GLib automatically tries to load gvfs plugins - but pressure-vessel doesn't actually need those plugins (and in fact tries to turn them off!), so it isn't a problem that it can't.

Newer versions of Steam Runtime 1 'scout' have a backported patch in GLib that can be used to avoid this, but because it's only cosmetic and does not affect the ability to run games, joining the dots has not been a high priority.

[cerealbox]

if it helps anyone else i was eventually able to get proton 5.13 to launch games using the steps in this comment as well:
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-710737373

i uninstalled, deleted and reinstalled proton and Steam Linux Runtime - soldier multiple times.
i also set the default proton version to 5.13 in steam settings -> steam play.
i am not sure though, specifically, what step resulted in success.

[oblitum]

i also set the default proton version to 5.13 in steam settings -> steam play.

good catch, I forgot to mention I had it as default too (even though it was removed and installed again in the process).

[earldbjr]

@kisak-valve, @gardotd426
ok, yes, finally. You were both right, there were bunch of leftover libs not cleaned up properly from 440.100
List

I fed this to rm, restarted Steam and now the games work in 5.13. I didnt even have to reinstall proton/soldier.
What a silly issue.

NOTE: before removing files found with find/grep, its advisable to first check if there are packages who own them and remove packages instead.

This resolved my problem as well. went to /usr/lib/ did a rm *440.100 (after ls-ing to make sure it was safe), rebooted, and voila everything works.

Kubuntu 20.04

[matheusreich]

Well, I am also having problems, but I am not using an NVIDIA GPU, but an AMD RX 580, so MESA. Only a couple of games actually runs on 5.13, like Cuphead, but Euro Truck Simulator 2 (which ran perfectly fine on DX11 with Proton 5.0-9) won't work at all.

[gardotd426]

Well, I am also having problems, but I am not using an NVIDIA GPU, but an AMD RX 580, so MESA. Only a couple of games actually runs on 5.13, like Cuphead, but Euro Truck Simulator 2 (which ran perfectly fine on DX11 with Proton 5.0-9) won't work at all.

The problems aren't limited to Nvidia. There are all sorts of fixes listed here, only the most recent one mentioned has anything to do with Nvidia.

[BdMdesigN]

In my case Steam don't find the Steam Linux Runtime - Soldier:
"soldier runtime container" is not installed.

Maybe the Soldier Runtime is installed as a Game and not as a Tool?
And yes Soldier is installed.

[frostworx]

But Proton 5.13 breaks compatibility tools like steamtinkerlaunch etc.

This is simply wrong, in fact steamtinkerlaunch works excellent with proton-5.13 and IMHO is currently the best option to test any issues with proton-5.13.

Looks almost like an embarrassing revenge attempt, as I lost my patience here after several hours hand holding.

[afettouhi]

But Proton 5.13 breaks compatibility tools like steamtinkerlaunch etc.

This is simply wrong, in fact steamtinkerlaunch works excellent with proton-5.13 and IMHO is currently the best option to test any issues with proton-5.13.

Looks almost like an embarrassing revenge attempt, as I lost my patience here after several hours hand holding.

I have no idea why you are claiming that this is a revenge attempt? I am again just expressing my experience with Proton 5.13 and steamtinkerlaunch. Granted I have only tested two games with stl and Proton 5.13, so my statement maybe a bit broad.

[MageFromAntares]

I was unable to launch any game with Proton 5.13 including the ones which were working with 5.0-9, the games attempted were:

• Empyrion - Galactic Survival
• Supreme Commander: Forged Alliance
• Warhammer 40k: Dawn of War - Dark Crusade
• Syberia The World Before - Prologue

All games fail the same way, press the play button->nothing happens->play button goes back to green.

I have attempted to generate a log file with PROTON_LOG, but no log file appears. (The log file is generated properly for 5.09).

Fixes already attempted:

1. kernel.unprivileged_userns_clone : Already set at 1
2. Deleting nvidia-driver 440.100: Not installed
3. Remove steam-native-runtime: Not installed
4. Uninstall then re-install Proton 5.13 and the Steam Runtime - Soldier : No change

Is there another way to generate logs other than setting PROTON_LOG=1?

Systeminfo attached:
steam-systeminfo-redacted.txt

[asdf-qwert]

Fixed it on my side.

• close steam
• uninstall steam-native-runtime (uninstalled recursively, which also removed steam, since I only used steam-native since I can't remember when)
• start steam
• removed all proton versions
• removed all Steam Linux Runtime - Soldier versions
• If removing those items from inside steam fail for any spurious issues (most probably it will), close steam, and remove each one that failed, manually (rm -rf the app directory and the appmanifest).
• start steam (clean with no native runtime nor any proton or soldier)
• launched Batman Arkham Knight. It installed Proton 5.13 automatically, but fails to load the game.
• launched Batman Arkham Knight, again. It installed the Soldier thing this time, automatically. Game loads.

This.
I also tried reinstalling everything multiple times and it did not work.
Today I gave it one more shot.
I have moved all Proton versions to the folder where steam is installed (~/.steam/steam/steamapps/) from all my disks which some of them are ntfs then I deleted all the Proton versions and the Runtime Soldier (some could be deleted through steam some had to be removed manually with associated .acf files) and installed everything again and the version 5.13 works!
Before it gave me "wine: could not load kernel32.dll, status c0000135"
Kubuntu 20.04

[gardotd426]

I really wish people would accept the fact that NTFS is not supported and
stop trying to use it.

On Thu, Oct 22, 2020 at 5:11 PM asdf-qwert [e-mail] wrote:

Fixed it on my side.

• close steam
• uninstall steam-native-runtime (uninstalled recursively, which also
  removed steam, since I only used steam-native since I can't remember when)
• start steam
• removed all proton versions
• removed all Steam Linux Runtime - Soldier versions
• If removing those items from inside steam fail for any spurious
  issues (most probably it will), close steam, and remove each one that
  failed, manually (rm -rf the app directory and the appmanifest).
• start steam (clean with no native runtime nor any proton or soldier)
• launched Batman Arkham Knight. It installed Proton 5.13
  automatically, but fails to load the game.
• launched Batman Arkham Knight, again. It installed the Soldier thing
  this time, automatically. Game loads.

This.
I also tried reinstalling everything multiple times and it did not work.
Today I gave it one more shot.
I have moved all Proton versions to the folder where steam is installed
(~/.steam/steam/steamapps/) from all my disks which some of them are ntfs
then I deleted all the Proton versions and the Runtime Soldier (some could
be deleted through steam some had to be removed manually with associated
.acf files) and installed everything again and the version 5.13 works!
Before it gave me "wine: could not load kernel32.dll, status c0000135"
Kubuntu 20.04

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-714764705,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y335CTHCFKGXPHWNXQ4DSMCNY5ANCNFSM4STRMDRA
.

[techmouse]

No luck here. I moved Proton 5.13 to my home hdd, uninstalled soldier, restarted steam, and ran a windows game from another ext4 partition. It still didn't start. It launched and immediately closed without anything happening. Just to verify, I double checked and soldier was indeed installed on an ext4 partition, too.

I also moved another windows only game to my home hdd just to see if there was a problem running games from other hdds or paths besides $HOME/.steam, and it still didn't run there either. So where games, Proton, and other tools are installed doesn't seem to make a difference.

I completely took NTFS out of the picture and still had no luck. NTFS is unrelated on my end. Additionally, I don't even see how it can be unsupported. Can windows even install on any file system besides NTFS, FAT32, or FAT16? How can it be unsupported if that's the best the windows side of things can do OOB?

[gardotd426]

Additionally, I don't even see how it can be unsupported. Can windows even install on any file system besides NTFS, FAT32, or FAT16? How can it be unsupported if that's the best the windows side of things can do OOB?

Seriously?

This isn't Windows. This is Linux. Linux doesn't use NTFS. Using Proton isn't using Windows. It's using Linux. You're never running any Windows code. The game's code that's intended to run on Windows is translated to Linux calls. So why the hell would it matter that Windows uses NTFS? This isn't Windows.

Valve has never supported NTFS with Proton. You may just now be having issues, but it's always been unsupported, for good reason, and going forward it looks like you won't even be able to "make" it work.

When you're trying to play games on Linux, you use Linux filesystems.

[techmouse]

You may just now be having issues, but it's always been unsupported, for good reason, and going forward it looks like you won't even be able to "make" it work.

But... I'm _not_ having problems with NTFS. Like I said, I've completely removed it from the equation and the problem persists. So that means NTFS isn't the problem.

And as far as the game developers are concerned, they only support windows, and the most advanced file system windows supports OOB is NTFS, so the developers support NTFS. So of course NTFS can't be unsupported.

NTFS is problematic, but it doesn't seem to be the problem here. At least not on my end.

[BdMdesigN]

Steam 4 Linux support only ext4 Filesystems. And you should NOT use NTFS under Linux. Why? Because the Linux file permissions dont't works on NTFS.

[techmouse]

But you _can_ set permissions on NTFS, while mounting from both the command line and fstab. And NTFS has been fine for external drives for years. It was the number 1 way duel booters would share common user files between Linux and windows.

• Get 1 or 2 small SSDs to install Linux and windows to (for fast boots)
• Get a large HDD for user files and make it NTFS
• Both OS's can safely access the same large HDD

This was the recommended method by the Linux community for years. And before SDDs existed, it was still the same but with small HDDs in place of SSDs.

NTFS is fine. Just don't install Linux to, or put your home directory on, a NTFS partition. And of course ext4 is far better, so if you can avoid NTFS, use ext4 instead. But that should go without saying, so I don't know why I have to say it.

[soredake]

@techmouse >ntfs is fine
Not for compatdata folder https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows#preventing-ntfs-read-errors

[gardotd426]

No, NTFS is not fine.

If you don't intend to play any Windows games, and you're using it in a limited capacity, fine. But Valve do not support running games from NTFS partitions on Linux. It's not complicated.

[techmouse]

@techmouse >ntfs is fine
Not for compatdata folder https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows#preventing-ntfs-read-errors

Did you even read it?

THERE HAS BEEN A REPORT THAT THIS MAY CAUSE DATA LOSS

A REPORT

One report.

creating files/folders with characters Windows cannot read will cause disk errors (leading to games that don't launch), the most common issue is a ; character in filenames

So because of invalid characters then? Invalid characters have existed throughout the decades. They're not specific to NTFS, windows, or even ext4 or Linux. And the solution has always been the same; just don't use them. Don't use them as a user, and don't write programs that use them as a programmer. Is that what this is all about? Did I just solve it? The game devs already expect it to be NTFS and windows, so why insist on making this a problem? Because we absolutely must use a ";" in a file name? Sounds kinda nutty to me.

Valve do not support running games from NTFS partitions on Linux. It's not complicated.

And Bethesda does not support running their games on Linux, but we're doing it anyways. "Complicated" is exactly how situations like this can be described.

Moving on...

Just to verify NTFS isn't the problem (again), I just now moved a game and proton 5.13 to ext4. Then deleted the soldier runtime and the game's compatdata, and made sure everything was installed on the same ext4 drive. Then I tried to run the game, and it still opened and immediately closed. I checked the game's compatdata and saw it was an empty folder.

I then switched the game to proton 5.0, ran it, and manually closed it. Everything worked smoothly. Proton 5.0 setup the compatdata folder properly and the game ran as expected. With the compatdata folder properly setup, I then switched it back to 5.13 again, and ran it, and it again opened and immediately closed with nothing happening.

The problem persists with NTFS completely removed from the situation, which again means NTFS isn't the problem. So why are we talking about NTFS?

I get the feeling you guys aren't taking this seriously. Let's get back on topic and stop arguing about NTFS. Only useful comments please.

[gardotd426]

Opt into the Steam Client Beta and let Steam update. Then try again. The
Beta client received updates to the Soldier runtime today.

And when you get it working, try running games from an NTFS partition.

On Fri, Oct 23, 2020 at 3:19 PM Mouse [e-mail] wrote:

@techmouse https://github.com/techmouse >ntfs is fine
Not for compatdata folder
https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows#preventing-ntfs-read-errors

Did you even read it?

THERE HAS BEEN A REPORT THAT THIS MAY CAUSE DATA LOSS

A REPORT

One report.

creating files/folders with characters Windows cannot read will cause disk
errors (leading to games that don't launch), the most common issue is a ;
character in filenames

So because of invalid characters then? Invalid characters have existed
throughout the decades. They're not specific to NTFS, windows, or even ext4
or Linux. And the solution has always been the same; just don't use them.
Don't use them as a user, and don't write programs that use them as a
programmer. Is that what this is all about? Did I just solve it? The game
devs already expect it to be NTFS and windows, so why insist on making this
a problem? Because we absolutely must use a ";" in a file name? Sounds
kinda nutty to me.

Valve do not support running games from NTFS partitions on Linux. It's
not complicated.

And Bethesda does not support running their games on Linux, but we're
doing it anyways. "Complicated" is exactly how situations like this can
be described.

Moving on...

Just to verify NTFS isn't the problem (again), I just now moved a game and
proton 5.13 to ext4. Then deleted the soldier runtime and the game's
compatdata, and made sure everything was installed on the same ext4 drive.
Then I tried to run the game, and it still opened and immediately closed. I
checked the game's compatdata and saw it was an empty folder.

I then switched the game to proton 5.0, ran it, and manually closed it.
Everything worked smoothly. Proton 5.0 setup the compatdata folder properly
and the game ran as expected. With the compatdata folder properly setup, I
then switched it back to 5.13 again, and ran it, and it again opened and
immediately closed with nothing happening.

The problem persists with NTFS completely removed from the situation,
which again means NTFS isn't the problem. So why are we talking about NTFS?

I get the feeling you guys aren't taking this seriously. Let's get back on
topic and stop arguing about NTFS. Only useful comments please.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-715534381,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y33YTXNBWNFZRRJ4W7IDSMHJMDANCNFSM4STRMDRA
.

[techmouse]

Opt into the Steam Client Beta and let Steam update. Then try again. The Beta client received updates to the Soldier runtime today. And when you get it working, try running games from an NTFS partition.

First, what would that prove? That the beta is buggy? Yeah, it probably is. That's why it's still in beta. NTFS wouldn't have anything to do with that.

Second, why are you still talking about NTFS? You have this weird axe to grind against it and it's not helping anything here. Focus on the topic at hand.

[kisak-valve]

Hello @techmouse, let's ponder some logs together. Please add PROTON_LOG=1 %command% to a game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

Just to verify NTFS isn't the problem (again), I just now moved a game and proton 5.13 to ext4. Then deleted the soldier runtime and the game's compatdata, and made sure everything was installed on the same ext4 drive. Then I tried to run the game, and it still opened and immediately closed. I checked the game's compatdata and saw it was an empty folder.

In terms of troubleshooting, moving games on and off of NTFS does sound fishy. If a filesystem handling quirk had happened between Proton and NTFS, it'd probably be persistent if copied elsewhere. I think if you deleted the dist folder at <Steam Library>/common/Proton 5.13/dist, then Proton should re-unpack itself from proton_dist.tar.

@gardotd426, there's no hard requirement for users to use EXT4, however, we do know that a lack of filesystem driver features makes NTFS finicky in several cases and FAT32 is incompatible with Proton due to a lack of symlink support.

[techmouse]

Please add PROTON_LOG=1 %command% to a game's launch options

I can't. It closes before Proton does anything, like I said in the exact block you quoted:

Just to verify NTFS isn't the problem (again), I just now moved a game and proton 5.13 to ext4. Then deleted the soldier runtime and the game's compatdata, and made sure everything was installed on the same ext4 drive. Then I tried to run the game, and it still opened and immediately closed. I checked the game's compatdata and saw it was an empty folder.

It doesn't even set up the compatdata directory.

please copy your system information from Steam (Steam -> Help -> System Information)

https://pastebin.com/kfQusnLF

In terms of troubleshooting, moving games on and off of NTFS does sound fishy. If a filesystem handling quirk had happened between Proton and NTFS, it'd probably be persistent if copied elsewhere. I think if you deleted the dist folder at <Steam Library>/common/Proton 5.13/dist, then Proton should re-unpack itself from proton_dist.tar.

I did. Like I said in the exact block you quoted above. I deleted the proton 5.13 install, the compatdata directory, and even the soldier runtime, moved and installed all 3 to my home partition(ext4) along with the windows game, and tried to run the game again. Same results.

Is anybody even reading my posts before responding? Are we just having a good time with our thumbs down emotes? I feel like I'm the target of a practical joke here.

[kisak-valve]

There's CClientJobGatherRuntimeInformation: container read output failed in your system information where it should have tried to gather information about Steam Linux Runtime - Soldier. This tells us there's an issue with running pressure-vessel on your system. There might be some hints if you completely close Steam, then run Steam from a terminal. It looks like you're using the distro-modified Steam package, so those hints might get intercepted and put in ~/.steam/error.log.

[techmouse]

There might be some hints if you completely close Steam, then run Steam from a terminal.

I did that the other day. The error it kept giving was:
CRASH (ACCESS VIOLATION (user-mode DEP violation):)
It just repeated that error any time I tried to run the game.

It looks like you're using the distro-modified Steam package

I probably am. I'm on KDE Neon, which is just Ubuntu with the latest KDE packages. The KDE team likely didn't modify the Steam package. But Ubuntu? I don't know what they're thinking anymore.

those hints might get intercepted and put in ~/.steam/error.log.

The only thing in error.log related to pressure-vessel is:

/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
assert_20201023193117_89.dmp[10804]: Finished uploading minidump (out-of-process): success = yes
assert_20201023193117_89.dmp[10804]: response: CrashID=bp-cc68da74-2e26-495a-8d83-aeebd2201023
assert_20201023193117_89.dmp[10804]: file ''/tmp/dumps/assert_20201023193117_89.dmp'', upload yes: ''CrashID=bp-cc68da74-2e26-495a-8d83-aeebd2201023''
i386-linux-gnu-capsule-capture-libs: code 2: Missing dependencies: Could not find "libwayland-server.so.0" in LD_LIBRARY_PATH "", ld.so.cache, /lib or /usr/lib
pressure-vessel-wrap[10807]: Child process exited with code 1
Installing breakpad exception handler for appid(steam)/version(1602795778)

The top line is talking about gnome virtual file system, gvfs. IIRC, that's used for mounting within userspace. Naturally it doesn't exist in a KDE environment. That's probably not related though, right? And of course I'm also not on wayland. Hopefully Proton doesn't expect either of those.

error.log:
https://pastebin.com/kx7GGim7

[gardotd426]

gvfs messages have been showing up in others' logs as well, idk if I would
read much into that.

On Fri, Oct 23, 2020 at 11:22 PM Mouse [e-mail] wrote:

There might be some hints if you completely close Steam, then run Steam
from a terminal.

I did that the other day. The error it kept giving was:
CRASH (ACCESS VIOLATION (user-mode DEP violation):)
It just repeated that error any time I tried to run the game.

It looks like you're using the distro-modified Steam package

I probably am. I'm on KDE Neon, which is just Ubuntu with the latest KDE
packages. The KDE team likely didn't modify the Steam package. But Ubuntu?
I don't know what they're thinking anymore.

those hints might get intercepted and put in ~/.steam/error.log.

The only thing in error.log related to pressure-vessel is:

/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
assert_20201023193117_89.dmp[10804]: Finished uploading minidump (out-of-process): success = yes
assert_20201023193117_89.dmp[10804]: response: CrashID=bp-cc68da74-2e26-495a-8d83-aeebd2201023
assert_20201023193117_89.dmp[10804]: file ''/tmp/dumps/assert_20201023193117_89.dmp'', upload yes: ''CrashID=bp-cc68da74-2e26-495a-8d83-aeebd2201023''
i386-linux-gnu-capsule-capture-libs: code 2: Missing dependencies: Could not find "libwayland-server.so.0" in LD_LIBRARY_PATH "", ld.so.cache, /lib or /usr/lib
pressure-vessel-wrap[10807]: Child process exited with code 1
Installing breakpad exception handler for appid(steam)/version(1602795778)

The top line is talking about gnome virtual file system, gvfs. IIRC,
that's used for mounting within userspace. Naturally it doesn't exist in a
KDE environment. That's probably not related though, right? And of course
I'm also not on wayland. Hopefully Proton doesn't expect either of those.

error.log:
https://pastebin.com/kx7GGim7

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/4278#issuecomment-715665341,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y332QEVLJOMEKJBLIBPDSMJB7PANCNFSM4STRMDRA
.

[aib]

Remember to check your syslog, folks.

Ubuntu 20.04.1; I wasn't getting proper error messages because proton itself wasn't running. Turns out it's a crash in pressure-vessel-launch:

Oct 24 00:01:49 vivaldi kernel: [360553.117404] pressure-vessel[879567]: segfault at 0 ip 0000000000000000 sp 00007ffd63479948 error 14 in pressure-vessel-launch[400000+14000]
Oct 24 00:01:49 vivaldi kernel: [360553.117408] Code: Bad RIP value.

Traced the crash to libgtk3-nocsd.so.0, which (being in LD_PRELOAD) attaches itself to every program in order to fix some issue with some GTK client side window decorations or something. I was tired of it showing up everywhere, so I uninstalled gtk3-nocsd and what do you know, proton started working again!

[kisak-valve]

@techmouse, i386-linux-gnu-capsule-capture-libs: code 2: Missing dependencies: Could not find "libwayland-server.so.0" in LD_LIBRARY_PATH "", ld.so.cache, /lib or /usr/lib pressure-vessel-wrap[10807]: Child process exited with code 1 is the line of interest in your log. That tells us that Pressure Vessel stopped while it was looking for additional dependencies that are needed to make the container runtime work properly. This is similar to https://github.com/ValveSoftware/steam-runtime/issues/275 and a fix for a driver variant of your issue is in the client_beta beta branch of Steam Linux Runtime - Soldier.

For clarity, this message is telling you that Steam Linux Runtime - Soldier was scanning the host system's libraries and a host system library was missing that dependency, not Pressure Vessel.

~In Steam's Library view, search for Soldier, open its per-game properties, then select client_beta on the beta tab and retest.~ The referenced fix has been promoted to the mainline branch.

Alternatively, you could try fixing the dependency with something like sudo apt install libwayland-server0:i386.

[Shished]

client_beta fixed problems for me, games are working now (I'm using Arch, BTW).

[BdMdesigN]

client_beta don't fix the problem for me

[smcv]

Traced the crash to libgtk3-nocsd.so.0

That preload library is known to break non-Steam programs quite regularly, too, and the GTK maintainers consider it to be a problem. I would recommend not using it.

If we do anything to solve that crash, it will probably be the brute-force approach: when we are adjusting LD_PRELOAD to work inside the container, remove any entry that looks like it might be libgtk3-nocsd.

[smcv]

/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new

Ignore this, it's harmless (GIO automatically loads the GVFS modules, but we don't actually need them for anything, and in fact we try to stop them from being loaded).

A future version of pressure-vessel will avoid this warning to reduce noise in issue reports, but it has been a lower priority than fixing things that actually harm games.

[Yarkhan]

Not sure if this is related, but Proton 5.13-1 was not working for me either. Found out Steam was not updating due bad permissions on some symlinks on ~/.steam/legacycompat.
I've renamed the files in the directory and restarted steam, and now everything is working correctly

[XirXes]

I was having this issue, and after getting the client_beta version of the Soldier runtime installed I was getting a little farther launching games but not quite. I found in the logs bwrap: No permissions to creating new namespace and found that depending on your setup you may need to grant bwrap the needed permissions by running # chmod u+s /usr/bin/bwrap. After that I was able to launch No Mans Sky and got some of the best performance I've ever had.

[nikolaos-spyratos]

Yeah, I've tried several of the workarounds here and elsewhere and many titles I play on Proton are currently broken no matter the version I use. Only common thread with them is the constant mentions of the LD_PRELOAD issue. Only other line that pops up for some games is:

[1030/143429.815000:ERROR:gles2_cmd_decoder.cc(8580)] [.DisplayCompositor]GL ERROR :GL_INVALID_ENUM : glFramebufferTexture2D: <- error from previous GL command

Apologies if this turns out to be the wrong cause but the only difference that has caused this is enabling the use of 5.13.

Broken:

• AC Origins/Odyssey: Can't find uplay installation when downgrading to 5.0-9, when on 5.13 it gets to the launch overlay and crashes. Even reinstalled, same issue.
• GTA V: Unable to find rockstar launcher when downgrading, "Unable to launch game, please verify your game data" on 5.13.
• Witcher 3: Doesn't launch, no errors
• Spyro Reignited: "Fatal error!" dialog.
• Crash Bandicoot N.Sane Trilogy: No visible error, just doesn't launch. Steam terminal output has a long register dump.
• Subnautica: Same as Crash.
• Endless Space 2: "The game crashed" dialog. Notable on this is that this was installed but never run, so first time setup and use of a specific proton version hadn't ever occurred. This would rule out any of local config changes.

Working:

• Sims 4: Just needed to reinstall Origin
• Age of Mythology Extended: No issues.

Gist for AC Odyssey is here
The errors above related to launchers not being found is usually resolved by just deleting the related compatdata folder and letting steam recreate it.

[murlakatamenka]

Proton games stopped working today (Arch), presumably removing steam-native-runtime fixed it. I didn't even know it was installed, I thought it was a part of steam package. I've been always launching steam via steam-runtime though. Hope it helps someone.

[BdMdesigN]

Ok i think i found the error in my case:

pressure-vessel-launch[26097]: Failed to start command: Failed to change to directory '/usr/local/games/Steam/steamapps/common/Metro 2033' (Datei oder directory nicht gefunden / file or dir not found)
My games are on a 8 TB HDD on a ext4 filesystem and mounted on /usr/local/games. My Steam Games are in /usr/local/games/Steam and pressure-vessel can't find it.

Steam Terminal Log: https://gist.github.com/BdMdesigN/14536143d24e1ce2400e8c4109c55988#file-steam-terminal-log

[kisak-valve]

Hello @BdMdesigN, please see https://github.com/ValveSoftware/steam-runtime/issues/288#issuecomment-717954844 / https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/issues/30.

[BdMdesigN]

Thanks for the Links @kisak-valve, i try to fix this with a Symlink from /usr/local/games/Steam/steamapps to ~.local/Steam/steamapps. Maybe it works.

Ok Symlinks don't works.

[nikolaos-spyratos]

Yesterday I even completely reinstalled Steam, just in case. I've also now tried overriding which runtime is used (back to scout) and still no luck across proton versions. compatlog.txt has nothing of interest, syslog has this for Odyssey no matter what I try. Right now only thing else I can do is wait for a runtime update and hope that fixes things.

[BdMdesigN]

Ok I had change the mount point yesterday from /usr/local/games to /opt/Games, so my Steam Games are in /opt/Games/Steam and pressure-vessel runs now. but the Games crashed with Proton 5.13 without a Protonlog

I thiks this is the needed Part from the Log:

`Opted-in Controller Mask for AppId 43110: 0
Game update: AppID 43110 "", ProcID 16083, IP 0.0.0.0:0
ERROR: ld.so: object '/srv/KeineAhnung/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
/bin/sh: /opt/Games/Steam/steamapps/common/Metro 2033/metro2033.exe: cannot execute binary file: Exec format error
Starting app 43110

Adding process 16083 for game ID 43110
GameAction [AppID 43110, ActionID 1] : LaunchApp changed task to WaitingGameWindow with ""
Adding process 16084 for game ID 43110
GameAction [AppID 43110, ActionID 1] : LaunchApp changed task to Completed with ""
Game removed: AppID 43110 "", ProcID 16083
Uploaded AppInterfaceStats to Steam
Exiting app 43110`

The problem i have in all Windows Games.

Metro 2033 Proton 5.13 Steam Beta Log: https://gist.github.com/BdMdesigN/2e1b68081d8eaff71f189d0bab10ee4c#file-metro-2033-proton-5-13-steam-beta-log-txt

Dump assert_20201101130226_142.dmp: https://filehorst.de/d/dzmpBmHC
Dump assert_20201101131553_147.dmp: https://filehorst.de/d/dwospfFE

[kisak-valve]

@BdMdesigN, /data/src/clientdll/compatmanager.cpp (844) : Assertion Failed: GetCompatibilityToolCommandLineInternal on dependent tool failed looks like a snafu we haven't seen before. I suspect that compatmanager.cpp is part of the Steam client, so please open a new issue report in the steam-for-linux to track that issue.

Setting that aside, this issue report has become a large tangle of several similar, but unrelated issues and this has become unmanagable. We've identified several issues between Proton 5.13 and Pressure Vessel and each individual issue should be tracked separately. We're going to need to close this issue without regard to the status of the follow up issues.

It looks like the original issue tracked here had something to do with Steam downloading and the first time setup of multiple Steam Play compatibility tools at the same time, which should have been improved in Steam.

For everybody else, if a log is not generated when running a game with PROTON_LOG=1 %command% in the game's launch options and it is set to use Proton 5.13, then there's a good chance that Pressure Vessel encountered an issue while initializing Steam Linux Runtime - Soldier.

We will be tracking Pressure Vessel issues in the steam-runtime issue tracker. This type of issue usually leaves a decent hint in the terminal spew which can be read if you completely close Steam, then run Steam from a terminal. The debian-modified Steam package can intercept that hint and put it in something like ~/.steam/error.log. If this is the case for anyone reading this issue report, please also search the steam-runtime issue tracker existing issues before opening a new issue report.