Steam for Linux

Steam for Linux

 Tämä aihe on kiinnitetty, joten se on todennäköisesti tärkeä
TTimo 10.11.2019 kello 13.11
Steam for Linux client adds support for Linux namespaces
The Steam client for Linux now supports using namespaces (a.k.a containers) to run game titles.

    This feature is available in the latest Steam client beta, and can be used for all native Linux titles in your Steam library.
    In order to run a title in a container, open the game's properties dialog, go to the general tab and select 'Steam Linux Runtime' under the 'Force the use of a specific Steam Play compatibility tool' drop down.

This new feature offers several advantages:

  • Titles are better isolated from the host system, improving a host of potential problems and enabling new features such as home isolation.
  • This feature improves Valve's ability to support older titles on newer distributions moving forward.
  • For developers, making sure your title runs in the container environment ensures better compatibility across multiple distributions, reducing your QA load.
  • For developers, Steam will be able to support newer runtimes via containers, which will include newer compilers and libraries.

How to use home isolation:

    Set PRESSURE_VESSEL_SHARE_HOME environment variable to 0 before running steam.

This is experimental! There are a few caveats:

  • Some titles will not run as-is in the container:

    Titles that do not run in the container can be reported to Valve at https://github.com/ValveSoftware/steam-runtime/

    Please provide a copy of your Help > System Information output when filing issues.

  • Proton over the container runtime is not supported yet.

  • The unofficial flatpak distribution of the Steam client is not compatible at this time.

    The flatpak solution wraps the entire Steam client, whereas Valve's approach is to wrap individual games first. Both approaches rely on the same technologies and we are looking into improving compatibility in the future.

  • Some of the more exotic graphics drivers setups like Bumblebee and Primus_VK will likely not work at this time.

    The container is setup to use the graphics drivers from the host system. We expect this release will bring us more testing coverage and identify various use cases that need to be improved.
Viimeisin muokkaaja on TTimo; 11.11.2019 kello 14.41
< >
Näytetään 1-15 / 35 kommentista
edmondo 10.11.2019 kello 14.26 
Nice! Thanks for working on this.
dbqp 10.11.2019 kello 15.05 
nice, I like the idea of containerized games in Steam
Viimeisin muokkaaja on dbqp; 10.11.2019 kello 15.06
Bloo Alien 10.11.2019 kello 15.08 
Right on. Nice to see Valve getting more familiar with and using Linux technologies more deeply. This should help with those games where developers pollute our home folders with "My Games" folders and other junk files.
Viimeisin muokkaaja on Bloo Alien; 10.11.2019 kello 15.10
Rednammoc 10.11.2019 kello 15.10 
Fantastic news! Looking forward to using this
maxtorete 10.11.2019 kello 15.10 
It's great to know a way to avoid Linux "fragmentation" problem is being worked on.

Thanks for your work.
Thanks for the hard work
nanokatze' 10.11.2019 kello 15.56 
At long last, Steam beginning to use Plan 9-st^Winspired features
Steam 64bits soon ?
I love you guys. This sounds awesome.
Cool, any performance hit ?
Bloo Alien 10.11.2019 kello 16.20 
GNU/LINUX facePlanted lähetti viestin:
Cool, any performance hit ?
Highly doubtful. Containers are about as lightweight as it gets. Should be the same as running outside a container. Just more safe and controllable.
pb 10.11.2019 kello 16.28 
Per-app containers are cool but what I'd like to see is per-app-per-steam-user containers. I have a SteamOS installation with three users and many games make a mess with saves and achievements, for example one user is playing a game, unlocks some achievements, then logs off, another user logs in and runs the same game, and the achievements unlocked by user#1 get unlocked for user#2 instantly. Same with (some) game saves etc. I tried various tweaks and they sometimes worked but not always.
pb 10.11.2019 kello 16.32 
Bloo Alien lähetti viestin:
This should help with those games where developers pollute our home folders with "My Games" folders and other junk files.

What I did was:
mkdir ~/saves ln -sf ../.steam ~/saves/ HOME=~/saves steam
and now all the 'homedir pollution' happens in ~/saves ;-)
Viimeisin muokkaaja on pb; 10.11.2019 kello 16.32
Bloo Alien 10.11.2019 kello 17.11 
pb lähetti viestin:
Bloo Alien lähetti viestin:
This should help with those games where developers pollute our home folders with "My Games" folders and other junk files.

What I did was:
mkdir ~/saves ln -sf ../.steam ~/saves/ HOME=~/saves steam
and now all the 'homedir pollution' happens in ~/saves ;-)
Oooooo! Tricky, tricky! That's a GOOD one! MUCH thanks for that there!

(Slick tricks like this to work around troublesome software is just one of the many reasons I love Linux.)
Viimeisin muokkaaja on Bloo Alien; 10.11.2019 kello 17.13
Will this also serve to sandbox games for security reasons à la Firejail, or would other steps be necessary to obtain that? Also, is this compatible with Firejail? I would suspect not, for the same reasons the Flatpak version is unsupported.
< >
Näytetään 1-15 / 35 kommentista
Sivua kohden: 15 30 50