ValveSoftware
Unable to use proton (games not loading)
Hi, let me preface this by saying that a) I do not use github very often, so sorry if I misplace something and b) this issue has been happening ever since July 16th 2022. After contacting steam support they asked me to submit here.
I will try to provide as much information as possible. I have recently been encountering a bug where every time I go to open up a game with proton steam either says the game is running and no window pops up, or the game will be stuck in the preparing to launch phase. Occasionally I also get stuck in installing vcredist for things like rocket league.
Native applications still work perfectly fine, so I believe this has to do with proton.
I have tried several different versions of proton on several different windows games, some of which I had previous run before, including proton 7.0-3, 6.3-8, 5.13-6, Experimental, GE (git), on games like rocket league, multiversus, BTD6, ori and the will of the wisps, risk of rain 2, all of which have the same errors on the proton versions.
I am currently running on arch with the 5.18.16 kernel, my computer hardware is as follows: -AMD Ryzen 5 3600 6 core -AMD Radeon RX 5700 -32gb of ram
-250gb nvme "boot" drive ssd - ext4 -1000gb m.2 "storage" drive ssd - ext4
Things I feel are important to note: -This occurred a couple days after switching from a Nvidia GTX 1650 Super to my current AMD Radeon RX 5700, games did in fact run during the short period where I just got my card though, so I don't think this is the issue, and yes I did fully remove nvidia drivers -This occurred a couple of days after changing BIOS settings to allow for resizable bar, I did change this back just to test however and it did not fix my issue -It's not a 32bit graphics driver issue, I have played other 32bit games on this boot -Lutris, and Wine are working perfectly fine
Things I have tried (I may have forgotten something) -Running steam, steam-runtime, in terminal to play games -Installing vcrun from proton tricks (Will not install) note this issue is happening on games that had already been installed and gone through first time setup -Moving files to my nvme drive -Reinstalling graphics drivers -Running steam-runtime --reset -Reading the terminal output of steam (I don't truely understand it so I will attach it) -Running steam games through wine in console (windows do open, most games instantly crash) -Installing steam through Lutris (did not work) -Resetting proton prefixes -Reinstalling proton -Reinstalling steam -Deleting steam data from home directory to 'reset' it -Running it through hyprland (did not fix any issues except ori and the will of the wisps ran for some reason)
I'm sure I missed something but I am currently at wit's end, so to speak, so any help would be greatly appreciated. I have attached 2 logs from console from when I attempted to run games. One from multiversus and one from BTD6.
Thank you to anyone who is reading this for your time, and I will check back here tomorrow. I do hope that this is fixable.
steamlog.txt btd6-steamlog.txt
I'm having the same issue, using Flatpak Steam on Openbox. I will say I've had a little bit of success trying to launch certain Unity engine games, in that they complain there's no D3DX11 compatible device installed, which might be a hint as to what the problem is. If mine turns out to be unrelated, I'll open a separate issue.
+1 I have had this issue in the past, both in KDE and Hyprland wm.
For me, running the game with a GE version of proton or using protonfixes to manually download whatever redists or whatever the game wants usually fixes the problem.
However, back when I first had this issue, none of these fixes helped, but I believe I accidentally deleted all of the compat data in steam (steamLibrary/steamapps/compatdata). Deleting this did two things, 1. forced me to reinstall all my games that were running through proton, and 2. made this issue go away
I have no idea what the cause for this could be...
Wanted to pop back in and say that manually updating my video drivers from nvidia-470 to nvidia-515 fixed it for me.
Hello @flippymusic, 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. Also, please add PROTON_LOG=1 %command% to the launch options of a couple games that worked previously, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Here is the system information output: https://gist.github.com/flippymusic/53d2a2e9a49fd6aa683120f5e91b3686
As for the proton logs, the games that get stuck in the "launching" state do not create logs which is pretty troublesome. The only way the games get past this point is by launching "steam-runtime" in the terminal and then opening games through that.
I did that with BTD6, and Rocket League, And I tried to log all 3 (edit: all three meaning the two previously mentioned games & risk of rain 2) normally and it didn't work.
Attaching the logs that I got, is there a way to force a log to be made? steam-960090.log steam-252950.log
A header only log hints that Proton encountered an issue before the actual game started to run. If you completely close Steam, then run steam-runtime from a terminal, are there any hints in the terminal spew when you tell Steam to start the game?
Yes, in the original text files I attached when I started this post, steamlog.txt shows everything that happens from the command to the game launch (in this case multiversus), the BTD6-steamlog.txt is just the part from when I open BTD6.
I consistently get "wrong ELF class" errors, as well as "Installing breakpad exception handler for appid(steam)/version(1658944613)" when launching a game. I don't really understand most of what it's saying, so could you take a look for me?
This might be worth pondering.
wine client error:0: version mismatch 743/635.
Your wine binary was not upgraded correctly,
or you have an older one somewhere in your PATH.
Or maybe the wrong wineserver is still running?
ERROR: ld.so: object '/home/liam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. This is a red herring - https://github.com/ValveSoftware/steam-for-linux/issues/6718.
Installing breakpad exception handler for appid(steam)/version(1658944613) lines are uninteresting.
I have a feeling that this bug might be what I'm experiencing. Under flatpak and Proton Experimental, a lot of my games do not run, complaining of lack of DirectX 11 compatibility.
If I switch to Pronton 7.0.3 or I use natively installed steam with Proton Experimental, everything seems to work.
I wonder if the flatpak version of steam is missing some libraries.
Hello @SuperMatt, the build of DXVK and VKD3D-Proton in Proton Experimental now requires mesa 22.0 or NVIDIA 510.47 or newer. Steam inside of Flatpak does not provide a new enough version of mesa. This is unrelated to the issue reported here.
This might be worth pondering.
wine client error:0: version mismatch 743/635. Your wine binary was not upgraded correctly, or you have an older one somewhere in your PATH. Or maybe the wrong wineserver is still running?
ERROR: ld.so: object '/home/liam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.This is a red herring - ValveSoftware/steam-for-linux#6718.
Installing breakpad exception handler for appid(steam)/version(1658944613)lines are uninteresting.
I'll be home in a couple of hours, how can I check to see if this is the issue?
I'm home, I deleted my wine prefixes, but it is still not working. Using wine --version through terminal gives me 7.14. Also I'm not getting that specific error anymore in the terminal output.
Any ideas on what to do from here?
Same here, I am trying to run multiversus on pop-os 22.04 using a Radeon RX 550 and I get this error
same error on archlinux, yesterday i'm surfed 4h in internet for finding fix, but don't found it
something is definitely misconfigured on your systems since my intel hd 4000 doesn't run into these problems, and it doesn't even support vulkan properly!
what does vulkaninfo --summary say?
something is definitely misconfigured on your systems since my intel hd 4000 doesn't run into these problems, and it doesn't even support vulkan properly! what does
vulkaninfo --summarysay? @Etaash-mathamsetty Here you go, I run on pop-os 22.04 and using an RX 550
vulkaninfo
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
==========
VULKANINFO
==========
Vulkan Instance Version: 1.3.204
Instance Extensions: count = 19
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
Instance Layers: count = 2
--------------------------
VK_LAYER_MESA_device_select Linux device selection layer 1.3.211 version 1
VK_LAYER_MESA_overlay Mesa Overlay layer 1.3.211 version 1
Devices:
========
GPU0:
apiVersion = 4206796 (1.3.204)
driverVersion = 92274693 (0x5800005)
vendorID = 0x1002
deviceID = 0x67ff
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = AMD RADV POLARIS11
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 22.0.5
conformanceVersion = 1.2.7.1
deviceUUID = 00000000-0900-0000-0000-000000000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
GPU1:
apiVersion = 4202700 (1.2.204)
driverVersion = 1 (0x0001)
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 13.0.1, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 22.0.5 (LLVM 13.0.1)
conformanceVersion = 0.0.0.0
deviceUUID = 00000000-0000-0000-0000-000000000000
driverUUID = 00000000-0000-0000-0000-000000000000
Replying to https://github.com/ValveSoftware/Proton/issues/6076#issuecomment-1214227509
Check what is your default gpu, you can run vkcube to check this, if it runs on lavapipe rather than your actual gpu, then something is wrong
My vulkaninfo --summary and vkcube are both telling me the correct GPU, along with up to date mesa drivers.
Here is the system information output: https://gist.github.com/flippymusic/53d2a2e9a49fd6aa683120f5e91b3686
As for the proton logs, the games that get stuck in the "launching" state do not create logs which is pretty troublesome. The only way the games get past this point is by launching "steam-runtime" in the terminal and then opening games through that.
I did that with BTD6, and Rocket League, And I tried to log all 3 (edit: all three meaning the two previously mentioned games & risk of rain 2) normally and it didn't work.
Attaching the logs that I got, is there a way to force a log to be made? steam-960090.log steam-252950.log
these all seem to be different issues, but yours is caused by proton refusing to init, I remember having this issue with aimlab once, it just magically fixed itself after doing a bunch of stuff to debug. I would try switching between lots of proton versions and verifying your proton installation along with the steam runtime installation. I would also make sure to delete the wine prefixes for those games. (they are in compatdata)
I would also fully uninstall steam (sudo pacman -Rns steam steam-runtime-native (removes dependencies too! beware!!)), remove .steam, and all other folder related to steam, and reinstall it
I would also install lib32-mesa and all the 32 bit drivers like lib32-vulkan-radeon
If all that doesn't work you are probably missing some 32 bit library
I have 32 bit drivers installed, and I have tried all of these which unfortunately did not work. Is there anything else you can think of?
@Etaash-mathamsetty here is the output, I am not sure how to decipher this Selected GPU 0: AMD RADV POLARIS11, type: 2
@Etaash-mathamsetty here is the output, I am not sure how to decipher this
Selected GPU 0: AMD RADV POLARIS11, type: 2
that's the correct GPU
I found this related issue, maybe try using wayland instead of xorg, or reverting the mentioned commit and making your own build of proton https://github.com/ValveSoftware/wine/issues/147
i reinstalled a clean Arch, put drivers and configurations, it helped me to run games with Steam Linux Runtime, but it is a bad solution because there is only support for opengl and vulkan, no dx11 and games like Dota 2 are not playing stable even with optirun, maximum 50 FPS. btw with Proton games still not launching (tried Proton Experimental and Proton 7.0-4, disabling steam overlay don't helps)
i reinstalled a clean Arch, put drivers and configurations, it helped me to run games with Steam Linux Runtime, but it is a bad solution because there is only support for opengl and vulkan, no dx11 and games like Dota 2 are not playing stable even with optirun, maximum 50 FPS. btw with Proton games still not launching (tried Proton Experimental and Proton 7.0-4, disabling steam overlay don't helps)
What gpu do you have, you should also provide other system specs, to help with troubleshooting. If u have an amd gpu, use radv instead of amdvlk. Maybe try using Wayland like i stated above Maybe proton 6.3-8 can fix your problem? Since the commit that i mentioned above is only in proton 7+
Replying to https://github.com/ValveSoftware/Proton/issues/6076#issuecomment-1221168015
GPU Nvidia GT 740M CPU Intel i5-4200M 4GB memory + 4GB swapfile HDD on 500GB
Proton 6.3-8 don't fixing problem.
Same here. This must be a regression as things were working a couple of days ago
Using updated Archlinux here
I've just remembered that I was able to play Among Us a couple of days ago.
I see btw wine64 process "sleeping on disk" on krunner's system monitor