Since I’ve installed Manjaro about a year ago, I’ve noticed a general inability to start most Windows games on Steam with Proton Experimental, 6.3, 5.13, and 5.0. Despite uninstalling them as tools on Steam, completely wiping their directories, uninstalling Steam, and reinstalling everything, they generally don’t work. Interestingly, 4.11 works fine for some games.
This hasn’t really bothered me because I built Proton-GE from AUR and this has satisfied most of my gaming needs. However, recently, I’ve been having issues with Proton-GE that has persisted through system reboots.
Similar to the other proton versions, hitting Play with Proton-GE enabled will instantly fail to boot up most games. This is after notably being able to play those same games with Proton-GE. A complete wipe and reinstall of GE will fix this issue, but I’m not a huge fan of having to do that every few days. I’m getting this in the game logs after using proton to log it:
======================
Proton: 1633118876 6.18-GE-2
SteamGameId: 632360
Command: ['/etc/drive2/SteamLibrary/steamapps/common/Risk of Rain 2/Risk of Rain 2.exe']
Options: {'forcelgadd'}
======================
ERROR: ld.so: object '/home/seacat/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/seacat/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/seacat/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/seacat/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
fsync: up and running.
ERROR: ld.so: object '/home/seacat/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
wine: failed to open L"C:\\windows\\system32\\wineboot.exe": c0000135
15540.118:0020:0024:err:environ:run_wineboot failed to start wineboot c0000135
wine: failed to load start.exe: c0000135
pid 18538 != 18537, skipping destruction (fork without exec?)
Again, this occurs after confirming the game has worked before with the same installation/version of Proton-GE before. The only thing of note that may happen after this is booting up a Windows VM with a second graphics card being passed through and playing some games there, then shutting it down. I’ve noticed this has caused some issues on some games.
All I gather from this is for some reason wineboot.exe and start.exe aren’t found. Any idea how to resolve this issue?
If you don’t want to fit to the FHS Standards, then you will get problems at some point and maybe now you have a problem because of this.
This is a so called “stopcode of windows” and normally you would get a nice bluescreen on windows because of this. However, what this means is: It cannot call start.exe because of some components/libraries cannot be loaded.
I’ve mounted my extra drives in /etc. Probably not the best choice to be honest, but I haven’t had any issues so far, and I can remount it somewhere else.
I don’t think that’s causing me any issues though, because I’ve had this setup for about a year now and am only recently having these proton issues.
Then you start a VM with the same GPU which has been used for proton before.
You shutdown the PC and start again. Now the games don’t work…
So judging, I would say the GPU cannot be used because it is running with the vfio-pci driver. Therefore the first GPU is in use which could be weaker or have no or not full vulkan support and only some games work.
Sorry, but without any hardware information, we can only grab our glass globes…
Steam Proton Versions are installed on the boot/main SSD. Location is: /home/seacat/.local/share/Steam/steamapps/common/Proton 6.3 and so on.
Proton-GE is installed: /usr/share/steam/compatibilitytools.d/proton-ge-custom which is there the AUR makefile places it.
If you mean installation location, no. The VM has a virtual HDD with separate installs.
Can you start the game with a more verbose log? The output above is a little lean.
I would expect that somehow the VM blocks the gpu on any level of execution, but I cannot be sure, since I see such a problem the first time. Or maybe symlinks are not there… However a verbose log could show which libaries wine is failing to call.
I’m afraid the most I can offer you is the terminal output when running steam from command line, I couldn’t find a way to make the proton logs more verbose:
GameAction [AppID 632360, ActionID 2] : LaunchApp changed task to ProcessingInstallScript with ""
wineserver: using server-side synchronization.
wine: failed to open L"C:\\windows\\system32\\wineboot.exe": c0000135
wine: failed to load start.exe: c0000135
GameAction [AppID 632360, ActionID 2] : LaunchApp changed task to SynchronizingCloud with ""
GameAction [AppID 632360, ActionID 2] : LaunchApp changed task to ProcessingShaderCache with ""
GameAction [AppID 632360, ActionID 2] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 632360, ActionID 2] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 632360, ActionID 2] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 632360, ActionID 2] : LaunchApp continues with user response "CreatingProcess"
/bin/sh\0-c\0PROTON_LOG=1 /home/seacat/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=632360 -- '/usr/share/steam/compatibilitytools.d/proton-ge-custom'/proton waitforexitandrun '/etc/drive1/SteamLibrary/steamapps/c
ommon/Risk of Rain 2/Risk of Rain 2.exe'\0
Game process added : AppID 632360 "PROTON_LOG=1 /home/seacat/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=632360 -- '/usr/share/steam/compatibilitytools.d/proton-ge-custom'/proton waitforexitandrun '/etc/drive1/St
eamLibrary/steamapps/common/Risk of Rain 2/Risk of Rain 2.exe'", ProcID 60680, IP 0.0.0.0:0
ERROR: ld.so: object '/home/seacat/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/seacat/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/seacat/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/seacat/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Loaded Config for Local Override Path for App ID 632360, Controller 0: /home/seacat/.local/share/Steam//controller_base/empty.vdf
GameAction [AppID 632360, ActionID 2] : LaunchApp changed task to WaitingGameWindow with ""
ProtonFixes[60681] INFO: Running protonfixes
ProtonFixes[60681] INFO: Running checks
ProtonFixes[60681] INFO: All checks successful
ProtonFixes[60681] INFO: Using global defaults for "Risk of Rain 2" (632360)
ProtonFixes[60681] INFO: No protonfix found for "Risk of Rain 2" (632360)
GameAction [AppID 632360, ActionID 2] : LaunchApp changed task to Completed with ""
Game process removed: AppID 632360 "PROTON_LOG=1 /home/seacat/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=632360 -- '/usr/share/steam/compatibilitytools.d/proton-ge-custom'/proton waitforexitandrun '/etc/drive1/S
teamLibrary/steamapps/common/Risk of Rain 2/Risk of Rain 2.exe'", ProcID 60680
Uploaded AppInterfaceStats to Steam
No cached sticky mapping in ActivateActionSet.No cached sticky mapping in ActivateActionSet.
At some point today I’ll try remounting my drives to their own folders in /ssd to see if that helps.
Interestingly enough, moving my mount point from /etc/drive1 to /sdd/drive1 has fixed the issues I’ve had with Proton 6.3 and other versions that wouldn’t work wholesale.
Still experiencing the same issue with Proton-Ge however.
Also maybe try to reset the Proton prefix for the games where it doesn’t work. Switching to different Proton version especially custom ones, can lead in issues in the prefix.
The prefix is the steamapps/compatdata/<game id> right? I’ve deleted that as well but when it regenerates still no dice for booting.
I’ll try what you suggested for Proton-GE.
Thanks for that link Sawdoctor, I’ll bookmark it.
Thanks Omano, I did what you said for Proton-GE and now it works flawlessly. I would say moving my mount location for my SDD with my game library from /etc to a mount directory in root /sdd fixed my issues with the Proton versions packaged with Steam.
Thanks for the help.
However, what this means is: It cannot call start.exe because of some components/libraries cannot be loaded.