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.

[mushiness2690]

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 notifications@github.com 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 notifications@github.com 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 notifications@github.com 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.