
What shitty site is this.

What shitty site is this.
This is bigger than it sounds for distros. The 32-bit Steam client was the main reason a lot of distros kept full 32-bit library support around. Ubuntu tried to drop i386 back in 2019 and walked it back largely because of Steam.
Older 32-bit games will still need those libraries, so multilib isn't going away tomorrow, but at least the client itself stops being the reason. And running it inside the runtime container should mean fewer "works on Arch, broken on Fedora" kinds of issues.
It really is! I think last year Fedora proposed dropping 32-bit and things almost got heated between them and Bazzite because of Steam still needed it. I forget why the Flatpak version of Steam didn't suite their needs, but I remember they had very good reasons why it wouldn't be an option to switch to.
I think with the option of running Steam on top/within of the new runtime would mean that they could drop multilib since the runtime can now provide it for the Steam Client (but dont quote me on that, the discussion i read is a little hazy).
Im really excited for the runtime change too, as a NixOS user, theres a bunch of weird issues that pop up due to the PATH thats a pain and time consuming to troubleshoot, rebuild, and test again. Everything is ironed out for normal stuff, but some of the things with 3rd party launchers or mods are messy.
Original announcement instead of blog spam: https://store.steampowered.com/news/app/593110/view/678515036155543747
It seems that multiarch and 32 bits packages are unfortunately still needed: https://mixed-news.com/en/steam-linux-client-64-bit-runtime-container-multilib-still-required/
I've been running it as a Flatpak, I wonder if this changes anything.
Anyone know if this removes the need for the Bubblewrap container on NixOS? That causes issues with asynchronous reprojection in Steam VR meaning you have to circumvent it with a different runtime (not ideal for if they ever let me order my Steam Frame)
I don't remember having to do that on my "Steam Machine" which is a desktop running NixOS. This is most of my "VR" module:
environment.systemPackages = with pkgs; [
iw
];
nixpkgs.config.allow32Bit = true;
# Steam Frame dongle requires a region be set to work
boot.extraModprobeConfig = ''
options cfg80211 ieee80211_regdom=ES
'';
# SteamVR requires CAP_SYS_NICE, this patch allows it to have it
# WARNING: This allows any application to create high priority contexts
boot.kernelPatches = [
{
name = "amdgpu-ignore-ctx-privileges";
patch = pkgs.fetchpatch {
name = "cap_sys_nice_begone.patch";
url = "https://github.com/Frogging-Family/community-patches/raw/master/linux61-tkg/cap_sys_nice_begone.mypatch";
hash = "sha256-Y3a0+x2xvHsfLax/uwycdJf3xLxvVfkfDVqjkxNaYEo=";
};
}
];
# SteamVR environment variables
environment.sessionVariables = {
# Force XCB platform for SteamVR under Wayland (prevents Qt Wayland issues)
QT_QPA_PLATFORM = "xcb";
};
It's been working with my Frame perfectly.
Ah, you're using the kernel patch, I've been a bit worried about that due to the security risks. It would be nice to be able to use it without it. Currently I'm using WiVRn (which uses the Monado runtime, fully FOSS which is nice) with a net-blocked Quest 2. I'm still on the waitlist for the Frame so I'll be lucky if I get one by 2030 anyway :(
But does the capsysnice thing has to do with it being 32 bits? I thought it was an independent issue.
Also, good luck with the wait-list, hopefully you'll get your email soon.
I'd love a Steam client that didn't tie up more RAM than most of the games I play
Yeah, I wonder if there's a way to disable the steam web browser to save RAM
steam is an electron app, itself needs a web browser to be displayed. you're essentially running chromium to run steam.
Is there anything without a container? It tanks on SLSA and violates iso27002.
all 18 comments