• SuperIce@lemmy.world
    link
    fedilink
    English
    arrow-up
    18
    ·
    1 day ago

    Doesn’t Steam run basically everything, including the client itself, inside the Steam Container Runtime now? No Steam games, native or not, use the system libraries anymore. I know I occasionally need to wait a couple of seconds after an update for it to update the Steam Container Runtime before even starting the client, which makes me think that they run the client in the container as well. I think the only real 32-bit dependency it has on the system is the user space graphics driver.

    • who@feddit.org
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      edit-2
      1 day ago

      Doesn’t Steam run basically everything, including the client itself, inside the Steam Container Runtime now?

      What makes you think that? I don’t remember any announcements to that effect.

      Last time I checked, Steam used pressure-vessel (the container) only for games, not for itself. But I haven’t been following changes in that area lately.

      • rtxn@lemmy.world
        link
        fedilink
        English
        arrow-up
        10
        ·
        edit-2
        1 day ago

        Through some script sleuthing, I did discover that Steam ships several of its own 32-bit and 64-bit libraries, and that paths to both are added to LD_LIBRARY_PATH (search path for library files) when the client is launched by the Steam Runtime, but many files (specifically the Steam Runtime) are only present as 32-bit binaries in ~/.local/share/Steam/ubuntu12_32.

        Whether the Steam client uses those is a question someone else less sleep-deprived can answer.