New Updates caused Steam games to fail starting

[sundaze]

Hello, I installed the updates which showed up in my Software Manager today. Since then, I can’t start up a single Steam game. Worked fine before the updates.

A few notes:

• my games are on external drives which are mounted on startup
• my external drives are formatted as NTFS (Known Problems with Linux) and it seems a similar Problem was posted regarding NTFS → Steam Proton Games do not start after last update → I am going to look into that.

However, since everything ran perfectly fine yesterday, I think it might have to to with either a driver or steam update that was included in the package.

Any suggestions on what I could do?

Here the terminal output on starting Vermintide 2 via steam:

fsync: up and running.
wine: failed to open "c:\\windows\\system32\\steam.exe": c0000135
chdir "/mnt/gamedrive/SteamLibrary/steamapps/common/Warhammer Vermintide 2/launcher/"
ERROR: ld.so: object '/home/sundaze/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cann
ot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Game Recording - would start recording game 552500, but recording for this game is disabled
Adding process 11705 for gameID 552500
ERROR: ld.so: object '/home/sundaze/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cann
ot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/sundaze/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cann
ot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/sundaze/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cann
ot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/sundaze/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cann
ot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Adding process 11706 for gameID 552500
Adding process 11707 for gameID 552500
WARNING: discarding _NET_WM_PID 5 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 5 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 5 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
Adding process 11794 for gameID 552500
ProtonFixes[11794] INFO: Running protonfixes on "GE-Proton10-34", build at 2026-03-23 03:55:11+00:00.
ProtonFixes[11794] INFO: Running checks
ProtonFixes[11794] INFO: All checks successful
ProtonFixes[11794] INFO: Using early stage global defaults for "Warhammer: Vermintide 2" (552500)
ProtonFixes[11794] INFO: No early stage global protonfix found for "Warhammer: Vermintide 2" (552500)
ProtonFixes[11794] INFO: Running protonfixes on "GE-Proton10-34", build at 2026-03-23 03:55:11+00:00.
ProtonFixes[11794] INFO: Running checks
ProtonFixes[11794] INFO: All checks successful
ProtonFixes[11794] INFO: Using main stage global defaults for "Warhammer: Vermintide 2" (552500)
ProtonFixes[11794] INFO: No main stage global protonfix found for "Warhammer: Vermintide 2" (552500)
Adding process 11795 for gameID 552500
Adding process 11801 for gameID 552500
fsync: up and running.
Adding process 11802 for gameID 552500
Adding process 11803 for gameID 552500
Adding process 11806 for gameID 552500
Adding process 11808 for gameID 552500
wine: failed to open "c:\\windows\\system32\\steam.exe": c0000135
pid 11804 != 11803, skipping destruction (fork without exec?)
Game Recording - game stopped [gameid=552500]
Removing process 11808 for gameID 552500
Removing process 11806 for gameID 552500
Removing process 11803 for gameID 552500
Removing process 11802 for gameID 552500
Removing process 11801 for gameID 552500
Removing process 11795 for gameID 552500
Removing process 11794 for gameID 552500
Removing process 11707 for gameID 552500
Removing process 11706 for gameID 552500
Removing process 11705 for gameID 552500

[Erim]

I vaguely remember similar issues, but I am not completely sure anymore how I solved it.

If I remember correctly something with the mount options regarding permissions to run executables changed. So I had to add the exec option when mounting.

[soundofthunder]

@sundaze

Any suggestions on what I could do?

Ideally, using a native Linux filesystem will be more resilient for your purposes – ext4 would be preferable, considering these games are stored on external disks.

Of course, the presumption is that you might be sharing the games between Windows and Manjaro – thus the choice of ntfs – this may be convenient, at face value, but as a result you will likely be plagued with these kinds of annoyances.

If you really must use ntfs, then you might find some information indirectly useful here, with respect appropriate mounting and permission management for ntfs:

[HowTo] Mount NTFS correctly under Linux

Difficulty: ★★☆☆☆ Avoid using NTFS on Linux whenever possible. But if you have no choice, you’ll want to get the most out of it – and that’s exactly why I wrote this. The main goal of this guide is to provide well-researched NTFS mount options that strike a balance between convenience and reasonable security – suitable for almost anyone. While the rest of the information can be found in countless other guides, the real value here lies in the options themselves and, unlike most NTFS guides, I…

However, another option is to use a exfat filesystem which, apart from being compatible with Windows, Linux and macOS, is not subject to permission issues.

The downside is that exfat isn’t as robust as ntfs, and any data recovery of damaged files is virtually impossible.

If my presumption is incorrect, and you’re not sharing the games between Windows and Manjaro, then reformat the external disk(s) as ext4 (as mentioned earlier).

Naturally, move the data to another location temporarily, as needed.

Please provide more information that may help others suggest any more immediate workrounds; see below.

Regards.

---

[Mini-HowTo] Provide System Information

Basic details provided by *-fetch type apps might give enough information for someone wishing to buy a computer, however, for Support purposes it’s best to ask your system directly.

Output of the inxi command will generate more useful and detailed information for those who may wish to help:

---

Suggested inxi command (use either):

inxi -zv8	(short-form)
inxi --filter --verbosity=8	(long-form)

• man inxi (The inxi manual)

---

Command output should be presented as pre-formatted text in accordance with forum guidelines.

---

Running inxi within a chroot environment

• Add --color=0 to the long-form command, or…
• Change the short-form command to inxi -zv8c0

Your privacy is respected

Run inxi using the --filter or -z parameters: personally identifiable information is filtered from the resulting output.

---

[Mini-HowTo] Present code or command output

Code or command output is expected to be presented similarly to how it would appear in a text editor (monospaced). The Discourse forum software makes it easy to create an enclosure (a text box) that is already pre-formatted for this purpose.

Note: Grave accent (or, backtick) characters are used.

For inline code or to show a single command:

• please follow this simple example: code here.

For multi-line command output:

• place text beween two rows of three (```) backtick characters to form a scrollable text box, or …
• use the </> button in the Compose window to achieve the same result.

Important: Click the </> button and paste text between the backticks (if using the old Compose layout). Otherwise, paste into the box generated (if using the new Compose layout).

The empty row between these rows of backtick characters is where to paste any multi-line command output (such as inxi).

An example of a pre-formatted text enclosure:

What is a Quark?

A. In Physics, an elementary particle and fundamental constituent of matter. 
B. A character from the Star Trek: "Deep Space Nine" television series.
C. A soft, creamy, usually unsalted cheese traditional to central Europe.

---

[sundaze]

Update: solved it.
Somehow the files in the Proton prefix for each game got corrupted or something.
I deleted them → Steam reinstalled them → now games run again.

However, I also formatted my drive to ext4. Just to be on the safe side for the next update

Thanks for the replies, gave me the needed courage to move my games around and free my 1tb drive for formatting