Related question - steam flatpak or deb?
this post was submitted on 03 Mar 2024
1 points (100.0% liked)
Linux Gaming
15292 readers
5 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 1 year ago
MODERATORS
What distro are you on?
Ubuntu 23.10
Steam downloads its own client updates. It's very rare for them to need to update the flatpak itself because usually any updates can be accomplished through the built in updater.
What about mesa drivers and other dependencies like Mangohud?
I'm not sure on the exact details of how it sources mesa, but you can check what version of mesa steam is using by clicking help in steam, and selecting "Steam Runtime Diagnostics". My flatpak steam install reports that I'm using Mesa 24.0.2-arch1.1, which is the same version I get if I check glxinfo | grep Mesa. I'm assuming that means flatpak Steam is using my system's mesa.
I do have some versions of Mesa installed through flatpak in the form of freedesktop.Platform packages, but they're older versions than what was reported from inside steam.
Great tip. It looks like the Flatpak has a newer version then even Tumbleweed, so that answers my initial question, thanks!
Components like that come from separate flatpaks (e.g. the Freedesktop Platform) or the Steam runtime (updated by Steam).
Makes sense, I was wondering how that worked when I saw some of those in my list. Is that another layer to the flatpak, like a Docker layer or are Flatpaks allowed out of their sandboxes to talk to other Flatpaks?
A flatpak can name extensions that are mounted into the running container if they're installed.
or are Flatpaks allowed out of their sandboxes
Be careful when thinking of flatpaks as sandboxes. What they confine is (by default) up to the maintainer of each flatpak, and most of the ones I have audited are very permissive.
You can mitigate this somewhat by editing the permissions of each flatpak before running it for the first time, with the command line or a GUI like flatseal. But that only goes so far, since some of the permissions are not fine-grained enough to provide meaningful sandboxing while still allowing games to run. (For example, shared memory and network access.) You might also consider creating a second linux account just for games, and logging in to that account's desktop when installing or running them.
A Flatpak container is better than nothing, and will probably keep you safe from most programming mistakes, but I wouldn't consider it a security/privacy sandbox by any means. If you want that, a hypervisor-based virtual machine would be better.
There's no way steam packages graphics drivers. That would be crazy, no?
My understanding is the Mesa driver is userland so Flatpaks can include it. I just assumed Steam would include it for slower moving distros.
I am new to Flatpaks and still trying to understand, any correction is welcome.
Mesa comes as separate flatpaks which is hidden in the GUI, and is automatically install when you install a flatpak. The system can have multiple versions of the driver installed. When Steam is ready to use a newer Mesa version, it will do it automatically.
Mangohud, on the other hand, is a flatpak you need to install manually via the command line. You should follow the instruction on their Github page for that.
P.S: In case you like a GUI for things. You should install Flatseal, which provide a GUI for configuring flatpaks.