Report: Proton games on Steam Flatpak breaking with white/transparent screen after NVIDIA driver update

System:
Zorin OS 18
NVIDIA RTX 4060
Driver 595.91.07
Steam via Flatpak

Symptom:
Overnight, with no config changes, games started breaking:
Spaceland: transparent screen, stuck
Dark and Darker: white screen (or black screen with audio)
Multiple games affected at once

What I ruled out:
Proton versions (tried 8.0-5, 9.0-3, 9.0-4, Hotfix, Experimental)
Kernel updates
Launch parameters
Wayland vs X11
Anti-cheat / GameThread

Diagnosis:
System driver was 595.91.07, but Flatpak had downloaded runtime 595-84, a mismatch. Games inside the sandbox had no 3D acceleration.

Fix:
flatpak update

This downloaded runtime 595-91-07, matching the system driver. Both games started working again.

Why:
Flatpak NVIDIA runtimes must match the system driver version. When they don't, Proton games lose GPU acceleration. Unity games show transparent screens, Unreal games show white/black screens.

For the future:
After any NVIDIA driver update, run flatpak update and check with flatpak list --runtime | grep -i nvidia

3 Likes

I am literately fighting the same battle, have not found a fix yet. I have Steam Deb installed straight off the Steam website and it has always been good to me on Zorin. I played a few games this morning came back a while later and now no games in my Lib works.

Tested the proton versions, with no success, updated, flushed cache, checked files integrity.

The flip side is i am on a modern AMD platform with a modern AMD GPU.

I shall keep the masses up to date on my findings.

Don not run Flatpaks it adds another layer of complexity.

Interesting that this is affecting AMD GPU, not just Nvidia... :thinking:

Going to reply to myself here:

After reading Journals, running logs, and and and.

Memo to myself: make sure to check and make sure Zorin didnt pull a sneaky on you and defaulted to wayland when logging in.

Swapped to Zorin Xorg and behold, all the troubleshooting was a waste of time.

Case closed

This is interesting... Other members, at least two others recently, have posted noting that their Xorg was switched at some point to Wayland without their knowledge. Was yours on Wayland all along and you did not realize it?
Or did it just... switch?

Might have been a fat finger moment when i was tinkering with the system.
I personally am not a big Wayland fan, it looks the part, but it can not play the part.
Xorg is far more mature.

Hope this post helps someone out there. :slightly_smiling_face:

1 Like

the version here is .deb not a flat pak alot seem to have more luck using the debian version