Steam silently fails

Support
1

This update seems to have broken steam for me; steam still launches, but any game I try to launch within it just silently fails to run. I tried following the advice of this referred thread to update an icon theme package, but the referred package was already installed: Steam games won't launch after 2024-10-10 stable update

This is using the stable steam package from Manjaro. The output of the steam process when run from the shell is:


chdir "/home/user/.local/share/Steam/steamapps/common/KingdomComeDeliverance2"
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
pid 5274 != 5273, skipping destruction (fork without exec?)
Game Recording - would start recording game 1771300, but recording for this game is disabled
Adding process 5273 for gameID 1771300
Game Recording - game stopped [gameid=1771300]
Removing process 5273 for gameID 1771300
Removing process 4885 for gameID 1771300
Adding process 5273 for gameID 1771300

The same error happens for any game I launch, not just this specific title. Has anyone else come across this? Thanks!

2

Just to follow up on this steam issue I had. It seems the update didn’t break steam for me, rather I had changed the fstab entry for my games partition to have the options: “noauto,user,rw” when before I had it as “defaults” only. Even though all the permissions in the mounted volume looked fine for steam, it could no longer execute within that mounted volume and was just silently not launching anything and printing those vague pid errors I posted here.

I ended up nuking all traces of steam from ~/.steam and reinstalling the package, and I then could not re-add my games drive through its storage settings, which led me down the path to this fstab issue. I must have made the edit at some point before running this major update.