u/Chaotic-Entropy

>Fedora Linux 44 (KDE Plasma Desktop Edition)
AMD Ryzen 7 9800X3D 8-Core Processor - RAM: 31 GB
AMD AMD Radeon RX 7800 XT (radeonsi, navi32, ACO, DRM 3.64, 7.0.11-200.fc44.x86_64) - VRAM: 16 GB

-----

**TL;DR: Runtime3 client "runs" but actually silently fails and runs with the default runtime.**

Is anyone successfully using the SteamRT3 Client? (Ideally on Fedora, or at least KDE)

I am struggling to get it to actually load correctly on all 3 of my Fedora 44 KDE devices, across both flatpak and the Fedora repo. I notice no difference when running straight without logging, but my Remote Play fails to work if I have it switched on.

If I run Steam in console then I get results which imply that actually, rather than running RT3 successfully, it is failing to run entirely and falling back on the default RT because I "don't have a valid steamrt64/steam executable". I get these logs:

[----] Verifying installation...
[2026-07-05 14:40:32] Verification complete
UpdateUI: skip show logo
Updating symlink: /home/peter/.steam/bin32 -> /home/peter/.local/share/Steam/steamrt32
Updating symlink: /home/peter/.steam/bin64 -> /home/peter/.local/share/Steam/steamrt64
Updating symlink: /home/peter/.steam/sdk32 -> /home/peter/.local/share/Steam/linux32
Updating symlink: /home/peter/.steam/sdk64 -> /home/peter/.local/share/Steam/linux64
Updating symlink: /home/peter/.steam/root -> /home/peter/.local/share/Steam/
Updating symlink: /home/peter/.steam/steam -> /home/peter/.local/share/Steam/
srt-logger: disabled, already open
ReexecToLauncher: opted into beta
ReexecToLauncher: opted into steamrt3 client
ReexecToLauncher: don't have a valid steamrt64/steam executable
ReexecToLauncher: proceeding in current environment
[2026-07-05 14:40:32] Shutdown
ReexecSteamLinux: received re-exec request with code: 67 steamrt: 0
ReexecSteamLinux: re-launching steam in SteamRT runtime

So:

• It verifies that my Client installation is correct.
• Remaps the steam executables.
• Fails to run the steamrt64/steam executable (despite the fact that it exists)
• Then falls back on the standard executable.

Unless I have missed something? Can anyone advise?

(I have flipped between beta modes, deleted and redownloaded all the RT3 files, it's across 3 different devices with different apps, etc. So doesn't seem that localised.)

>Fedora Linux 44 (KDE Plasma Desktop Edition)
AMD Ryzen 7 9800X3D 8-Core Processor - RAM: 31 GB
AMD AMD Radeon RX 7800 XT (radeonsi, navi32, ACO, DRM 3.64, 7.0.11-200.fc44.x86_64) - VRAM: 16 GB

-----

**TL;DR: Runtime3 client "runs" but actually silently fails and runs with the default runtime.**

Is anyone successfully using the SteamRT3 Client? (Ideally on Fedora, or at least KDE)

I am struggling to get it to actually load correctly on all 3 of my Fedora 44 KDE devices, across both flatpak and the Fedora repo. I notice no difference when running straight without logging, but my Remote Play fails to work if I have it switched on.

If I run Steam in console then I get results which imply that actually, rather than running RT3 successfully, it is failing to run entirely and falling back on the default RT because I "don't have a valid steamrt64/steam executable". I get these logs:

[----] Verifying installation...
[2026-07-05 14:40:32] Verification complete
UpdateUI: skip show logo
Updating symlink: /home/peter/.steam/bin32 -> /home/peter/.local/share/Steam/steamrt32
Updating symlink: /home/peter/.steam/bin64 -> /home/peter/.local/share/Steam/steamrt64
Updating symlink: /home/peter/.steam/sdk32 -> /home/peter/.local/share/Steam/linux32
Updating symlink: /home/peter/.steam/sdk64 -> /home/peter/.local/share/Steam/linux64
Updating symlink: /home/peter/.steam/root -> /home/peter/.local/share/Steam/
Updating symlink: /home/peter/.steam/steam -> /home/peter/.local/share/Steam/
srt-logger: disabled, already open
ReexecToLauncher: opted into beta
ReexecToLauncher: opted into steamrt3 client
ReexecToLauncher: don't have a valid steamrt64/steam executable
ReexecToLauncher: proceeding in current environment
[2026-07-05 14:40:32] Shutdown
ReexecSteamLinux: received re-exec request with code: 67 steamrt: 0
ReexecSteamLinux: re-launching steam in SteamRT runtime

So:

• It verifies that my Client installation is correct.
• Remaps the steam executables.
• Fails to run the steamrt64/steam executable (despite the fact that it exists)
• Then falls back on the standard executable.

Unless I have missed something? Can anyone advise?

(I have flipped between beta modes, deleted and redownloaded all the RT3 files, it's across 3 different devices with different apps, etc. So doesn't seem that localised.)

I was keeping an eye out for the 6.7 update of Bigscreen, as it was still showing the Feb build since 6.7 became available for Fedora. The latest build is now up installable with:

dnf in plasma-bigscreen

Looking forward to using this for my TV attached mini-pc.

That took less time than I expected. Though I don't see Plasma Bigscreen as available yet.

Should I be concerned about the encroachment of private equity leadership in to Bitwarden...?

I already have access to ProtonPass, but have always stuck with Bitwarden for its features and ethos. This does seem like something of a shift though, would be a shame to have to drop it.