Steam will not install. Error "unmet dependencies" on steam-libs-i386

I am looking to migrate my desktop machine to Linux as (like many I suspect) I don’t like Win 11 or what it brings with it. I have done the basic setup, but when I went to install Steam from the standard repo I ran into a problem.

There is no single “steam” package, so I went to install steam-installer but this failed with a number of “Broken steam-installer” errors, and then finally a failed dependency on steam-libs-i386. (see below for details)

Given the popularity of Steam it’s hard to believe that the source package is broken, so my guess is I may have a local configuration error, but i’m not sure how to track it down.

Full details of the error message are below. Note I have installed the nala frontend to apt and originally used that for the first attempted install, but I have included the output from running apt directly here as i’m guessing people will be more familiar with this format.

Ubuntu Version:
24.04 LTS

Desktop Environment (if applicable):
KDE Plasma

Problem Description:
Steam will not install from the standard Ubuntu repos

Relevant System Information:
Kernel Version: 6.11.0-17-generic (64-bit)
Graphics Platform: Wayland
Processor: Intel® Core™ i7-6700K
Memory: 32 GiB RAM
Graphics Processor: AMD Radeon RX 6700 XT
Motherboard: Z170X-GamingG1

Screenshots or Error Messages:
(note apt update has been run)

apt install steam-installer
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) steam-installer:amd64 < none -> 1:1.0.0.79~ds-2 @un puN Ib >
Broken steam-installer:amd64 Depends on steam-libs:amd64 < none | 1:1.0.0.79~ds-2 @un uH > (= 1:1.0.0.79~ds-2)
  Considering steam-libs:amd64 0 as a solution to steam-installer:amd64 9998
  Re-Instated steam-libs:amd64
Broken steam-installer:amd64 Depends on steam-libs-i386:amd64 < none @un H > (= 1:1.0.0.79~ds-2)
Broken steam-installer:amd64 Depends on zenity:amd64 < none | 4.0.1-1build3 @un umH >
  Considering zenity:amd64 1 as a solution to steam-installer:amd64 9998
  Re-Instated libcairo-script-interpreter2:amd64
  Re-Instated libgtk-4-common:amd64
  Re-Instated libgtk-4-1:amd64
  Re-Instated libadwaita-1-0:amd64
  Re-Instated zenity-common:amd64
  Re-Instated zenity:amd64
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 steam-installer : Depends: steam-libs-i386 (= 1:1.0.0.79~ds-2) but it is not installable
E: Unable to correct problems, you have held broken packages.
apt-cache showpkg steam-installer
Package: steam-installer
Versions: 
1:1.0.0.79~ds-2 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/mirrors.us.kernel.org_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/mirror.eu-lo.kamatera.com_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/mirror.eu.kamatera.com_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/ubuntu.mirrors.ovh.net_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/mirrors.gethosted.online_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/mirrors.xtom.nl_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/www.mirrorservice.org_sites_archive.ubuntu.com_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/mirror.ams.macarne.com_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/mirror.vinehost.net_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/ftp.fau.de_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/mirror.katapult.io_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/mirror.united-gameserver.de_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/mirrors.coreix.net_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/mirror.webworld.ie_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/ftp.klid.dk_ftp_ubuntu_dists_noble_multiverse_binary-amd64_Packages) (/var/lib/apt/lists/ubuntu.mirror.lrz.de_ubuntu_dists_noble_multiverse_binary-amd64_Packages)
 Description Language: 
                 File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_noble_multiverse_binary-amd64_Packages
                  MD5: 1628561328c024db73bb48ba285fc9ad


Reverse Depends: 
  game-data-packager,steam-installer
  steam-devices,steam-installer
Dependencies: 
1:1.0.0.79~ds-2 - debconf (0 (null)) steam-libs (5 1:1.0.0.79~ds-2) steam-libs-i386 (5 1:1.0.0.79~ds-2) zenity (16 (null)) yad (0 (null)) debconf (18 0.5) debconf-2.0 (0 (null)) steam-launcher (0 (null)) steam (3 1:1.0.0.75+ds~) steam (3 1:1.0.0.75+ds~) steam-launcher (0 (null)) 
Provides: 
1:1.0.0.79~ds-2 - 
Reverse Provides:

What I’ve Tried:
Used apt-cache showpkg to confirm that the pkg is from an appropriate repo. The top matches are from ubuntu.com, so I assume that’s ok

Use the Snap.

This is mentioned many times on this Discourse but here’s one such place:

1 Like

While using the snap is an option, it’s not the solution to the problem being asked.

@incans what’s the output of dpkg --print-foreign-architectures?

If it does not include i386 in the output then yes, there’s a configuration error on your system. I would recommend dpkg --add-architecture i386; apt update then sudo apt install steam-installer steam-libs-i386 and see if that works.

2 Likes

It’s been some years since I last set up a Linux box (a home server running Debian) and in that time one of the big changes has been the rise of these sandboxed app package formats like Flatpak, Snap and AppImage.

I have to say i’m not convinced. At least not now, maybe in a couple of years when one format has become dominant, and hopefully most of the bugs and limitations have been ironed out.

Early on in this setup, I installed KeePassXC, Firefox, and the LibreWolf variant of FF, all as Flatpaks. What I discovered from this after a couple of days of frustration was-

  • Sandboxed Apps (at least Flatpaks) DO NOT have the same functionality as “real” old-fashioned local apt installs. It turns out password autocompletion integration between KeePassXC and browsers is only supported when both applications are installed directly
  • The fact that sandboxed formats exist seems to be encouraging app developers (or the packaging teams for the distros) to let availability slide. As an example I couldn’t find an up to date Ubuntu repo or deb package for LibreWolf at all. Their default answer is “use the Flatpak”, but that’s only any use of you don’t want integration with KeePass.

So, minor rant over. dpkg --print-foreign-architectures prints nothing (no output).

a) Is that wrong?
b) If Steam needs something specific like 32 bit libraries as a dependency, isn’t that exactly what the dependency management of apt is supposed to deal with?

It’s not matter of right or wrong, Only if the system is able to use them, ie:


└─>  dpkg --print-foreign-architectures
┌───────────────────>

Now I’ll add that to the packaging system:


└─> sudo dpkg --add-architecture i386
┌───────────────────>
│~ 
└─>  dpkg --print-foreign-architectures
i386

Before *architecture i386

sudo apt install steam-installer
Solving dependencies... Error!  
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 steam-installer : Depends: steam-libs-i386 (= 1:1.0.0.82~ds-3) but it is not installable

After

sudo apt install steam-installer
Installing:                     
  steam-installer

Installing dependencies:
  gcc-15-base:i386              libpangoft2-1.0-0:i386
  i965-va-driver:i386           libpciaccess0:i386
  intel-media-va-driver:i386    libpcre2-8-0:i386
  libadwaita-1-0                libpixman-1-0:i386
  libaom3:i386                  libpng16-16t64:i386
  libapparmor1:i386             libpulse0:i386
  libasound2-plugins:i386       librsvg2-2:i386
  libasound2t64:i386            librsvg2-common:i386
  libasyncns0:i386              libsamplerate0:i386
  libatk-bridge2.0-0t64:i386    libsdl2-2.0-0
  libatk1.0-0t64:i386           libsdl2-2.0-0:i386
  libatomic1:i386               libselinux1:i386
  libatspi2.0-0t64:i386         libsensors5:i386
  libavahi-client3:i386         libsharpyuv0:i386
  libavahi-common-data:i386     libshine3:i386
  libavahi-common3:i386         libsnappy1v5:i386
  libavcodec61:i386             libsndfile1:i386
  libavutil59:i386              libsoxr0:i386
  libblkid1:i386                libspeex1:i386
  libbrotli1:i386               libspeexdsp1:i386
  libbsd0:i386                  libssl3t64:i386
  libbz2-1.0:i386               libstdc++6:i386
  libc6:i386                    libsvtav1enc2:i386
  libcairo-gobject2:i386        libswresample5:i386
  libcairo2:i386                libsystemd0:i386
  libcap2:i386                  libtasn1-6:i386
  libcodec2-1.2:i386            libthai0:i386
  libcolord2:i386               libtheoradec1:i386
  libcom-err2:i386              libtheoraenc1:i386
  libcrypt1:i386                libtiff6:i386
  libcups2t64:i386              libtinfo6:i386
  libdatrie1:i386               libtwolame0:i386
  libdav1d7:i386                libudev1:i386
  libdb5.3t64:i386              libunistring5:i386
  libdbus-1-3:i386              libusb-1.0-0:i386
  libdecor-0-0                  libva-drm2:i386
  libdecor-0-0:i386             libva-glx2
  libdecor-0-plugin-1-gtk       libva-glx2:i386
  libdecor-0-plugin-1-gtk:i386  libva-x11-2:i386
  libdeflate0:i386              libva2:i386
  libdrm-amdgpu1:i386           libvdpau1:i386
  libdrm-intel1:i386            libvorbis0a:i386
  libdrm-radeon1:i386           libvorbisenc2:i386
  libdrm2:i386                  libvpx9:i386
  libedit2:i386                 libvulkan1:i386
  libegl-mesa0:i386             libwayland-client0:i386
  libegl1:i386                  libwayland-cursor0:i386
  libelf1t64:i386               libwayland-egl1:i386
  libepoxy0:i386                libwayland-server0:i386
  libexpat1:i386                libwebp7:i386
  libffi8:i386                  libwebpmux3:i386
  libflac12t64:i386             libx11-6:i386
  libfontconfig1:i386           libx11-xcb1:i386
  libfreetype6:i386             libx264-164:i386
  libfribidi0:i386              libx265-215:i386
  libgbm1:i386                  libxau6:i386
  libgcc-s1:i386                libxcb-dri2-0:i386
  libgdk-pixbuf-2.0-0:i386      libxcb-dri3-0:i386
  libgl1:i386                   libxcb-glx0:i386
  libgl1-mesa-dri:i386          libxcb-present0:i386
  libglapi-mesa:i386            libxcb-randr0:i386
  libglib2.0-0t64:i386          libxcb-render0:i386
  libglvnd0:i386                libxcb-shm0:i386
  libglx-mesa0:i386             libxcb-sync1:i386
  libglx0:i386                  libxcb-xfixes0:i386
  libgmp10:i386                 libxcb-xkb1:i386
  libgnutls30t64:i386           libxcb1:i386
  libgomp1:i386                 libxcomposite1:i386
  libgpg-error0:i386            libxcursor1:i386
  libgraphite2-3:i386           libxdamage1:i386
  libgsm1:i386                  libxdmcp6:i386
  libgssapi-krb5-2:i386         libxext6:i386
  libgtk-3-0t64:i386            libxfixes3:i386
  libharfbuzz0b:i386            libxi6:i386
  libhogweed6t64:i386           libxinerama1:i386
  libidn2-0:i386                libxkbcommon-x11-0:i386
  libigdgmm12:i386              libxkbcommon0:i386
  libjack-jackd2-0:i386         libxml2:i386
  libjbig0:i386                 libxrandr2:i386
  libjpeg-turbo8:i386           libxrender1:i386
  libjpeg8:i386                 libxshmfence1:i386
  libk5crypto3:i386             libxss1:i386
  libkeyutils1:i386             libxvidcore4:i386
  libkrb5-3:i386                libxxf86vm1:i386
  libkrb5support0:i386          libzstd1:i386
  liblcms2-2:i386               libzvbi0t64:i386
  libllvm19:i386                mesa-libgallium:i386
  liblzma5:i386                 mesa-va-drivers:i386
  libmd0:i386                   mesa-vdpau-drivers:i386
  libmount1:i386                mesa-vulkan-drivers:i386
  libmp3lame0:i386              ocl-icd-libopencl1:i386
  libmpg123-0t64:i386           steam-devices
  libnettle8t64:i386            steam-libs
  libnm0:i386                   steam-libs:i386
  libnuma1:i386                 steam-libs-i386:i386
  libogg0:i386                  va-driver-all:i386
  libopenjp2-7:i386             vdpau-driver-all:i386
  libopus0:i386                 zenity
  libp11-kit0:i386              zenity-common
  libpango-1.0-0:i386           zlib1g:i386
  libpangocairo-1.0-0:i386

Suggested packages:
  i965-va-driver-shaders:i386  gvfs:i386            nvidia-driver-libs
  libcuda1:i386                jackd2:i386          nvidia-vulkan-icd
  libnvcuvid1:i386             cryptsetup-bin:i386  gtk2-engines-pixbuf:i386
  libnvidia-encode1:i386       opus-tools:i386      libgtk2.0-0t64:i386
  glibc-doc:i386               pulseaudio:i386      | libgtk2.0-0:i386
  locales:i386                 librsvg2-bin:i386    libudev0:i386
  libnss-nis:i386              lm-sensors:i386      nvidia-driver-libs:i386
  libnss-nisplus:i386          speex:i386           nvidia-vulkan-icd:i386
  low-memory-monitor:i386      libgcrypt20:i386     pipewire:i386
  gnutls-bin:i386              liblz4-1:i386        libvdpau-va-gl1:i386
  krb5-doc:i386                opencl-icd:i386
  krb5-user:i386               libudev0

Recommended packages:
  libgl1-amber-dri:i386

Summary:
  Upgrading: 0, Installing: 202, Removing: 0, Not Upgrading: 0
  Download size: 122 MB
  Space needed: 455 MB / 457 GB available

Continue? [Y/n] 


2 Likes

“Excellent”. We have solved the problem. Follow the steps I posted, or the ones @1fallen has made more pretty.

It is not wrong. It’s just not configured correctly for you to succeed in your expectations of i386 dependency package installation nirvana.

Yes, and it did. It worked perfectly as configured. It may not have been the outcome you desired or expected but it was the correct outcome given the prevailing configuration at the time.

In my mind, it went something like this:


The Tragic Tale of Steam Installation

A short play in one act

CHARACTERS

  • INCANS: A frustrated Linux user trying to migrate from Windows 11
  • APT: The package manager, efficient but literal-minded
  • DPKG: The lower-level package management system, precise and technical

SCENE

A sparse desktop environment. INCANS sits at a computer terminal, looking hopeful.


INCANS: (typing eagerly) Finally free from Windows 11! Let’s get Steam installed so I can play my games.

APT enters from stage left, wearing a uniform with many pockets labeled with package names.

APT: (formally) How may I assist you today?

INCANS: I’d like to install Steam, please.

APT: (checking through pockets) I see no single “steam” package. Perhaps you’d like steam-installer?

INCANS: (nodding) Yes, that sounds right.

APT: (calling offstage) DPKG! I need to check dependencies for steam-installer!

DPKG enters, carrying a clipboard and wearing spectacles.

DPKG: (adjusting spectacles) Checking dependencies… steam-libs, zenity, and… steam-libs-i386.

APT frowns and checks all pockets.

APT: (confused) I can find steam-libs and zenity, but steam-libs-i386?

DPKG: (checking clipboard) What foreign architectures are you currently supporting?

APT: (proudly) None! We’re purely amd64!

DPKG: (sighs) That would explain it.

INCANS: (concerned) Is there a problem?

APT: (formally) I regret to inform you that some packages could not be installed. This may mean that you have requested an impossible situation.

INCANS: But… but… Steam is popular! How could this be broken?

DPKG: (clearing throat) It’s not broken. It’s working exactly as configured.

APT: (musing philosophically) Foreign architectures… what a curious term. We’re all from the same computer, aren’t we? Why must we divide ourselves with these labels?

DPKG: (matter-of-factly) Because 32-bit and 64-bit binaries are fundamentally incompatible without proper configuration.

INCANS: (frustrated) So what do I do?

DPKG: (checking clipboard) You could add i386 as a foreign architecture.

APT: (gasps) Welcome immigrants into our system? How progressive!

DPKG: (rolling eyes) It’s just a technical requirement, not a political statement.

INCANS tries the command but doesn’t know what to do next and slumps down onto the floor.

INCANS: (despairing) All I wanted was to play my Steam games… my Linux migration dream is falling apart…

APT: (defensively) I did nothing wrong! I followed my programming exactly!

DPKG: (nodding) The system operated correctly within its configured parameters.

INCANS: (head in hands) But why couldn’t it just work?

APT: (straightening uniform) Because, dear user, you never told me to care about i386 packages.

DPKG: (adjusting glasses) Linux gives you the freedom to configure your system exactly as you want. The price of that freedom is that sometimes you need to know what you want.

Lights dim as INCANS remains sitting on the floor, APT and DPKG exit stage right.

CURTAIN


3 Likes

Wow. If I had the power to make badges here, I would be making one right now for Most Creative Post and granting it to you. What’s even more uncanny about it: it explains the truth of the matter perfectly.

2 Likes

Hats off to @popey for his brief diversion into playwritery. But I can’t help wondering why Valve (I assume it is they) are shipping 32 bit only packages in 2025?

I’m not suggesting that’s anyone’s responsibility here, i’m sure Valve march to their own drum, but it does seem a bit, erm, 1985?

Back to the original point, i’m grateful for the help in identifying the problem. I can’t help thinking that my idea of a clear error message and the views of the person/team that wrote apt don’t overlap to any great extent.

It would have been nice to see something like-

  • You need architecture i386
  • You don’t have architecture i386 and I can’t (or won’t) install it for you automatically
  • You can install architecture i386 with the command…

So, just to repeat I am grateful for the help. I will now hopefully continue on the journey. It would be nice to be able to run at least one game from Stream this week.

1 Like

Thanks.

There’s a very sensible and logical reason for it when you think about it. Steam contains thousands of games. Many of them have only ever been built and published by the game developer as 32-bit binaries. For many old games there simply are zero 64-bit builds.

Valve have a commitment. Every game is sacred. If you bought a game 10 or even 15 years ago, it should still work today, in 2025. Valve don’t have access to the source code for non-Valve games, and in many cases, neither do the original game publishers.

It’s very common for game developers to move on to the next project once a game is published. They may never even install the same tools again, and they might leave the company. So the chances of them dusting off the tools to build a 64-bit build at tremendous time and effort to them, for probably zero gain, well, it’s not worth it.

Steam (the client) has some bundled 32-bit libraries, provided by Valve. You can see them (once you get it installed) like this:

$ cd .steam/debian-installation/ubuntu12_32/
 …/.steam/debian-installation/ubuntu12_32 $ file lib*.so* | head
libaom.so.3:         ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=b5aeb48337857d5057a98d9e1434594e49fc658c, not stripped
libaudio.so:         ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=a225d47e32dbd1eace13017f9f1218d2b7dad89d, not stripped
libavcodec.so.58:    ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=7301d337a57482db88322b33ac4ed683cfd3b1e2, stripped
libavcodec.so.61:    ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=51bd113f41d59f4bc53e7e525eff60a7c34f90bf, stripped
libavfilter.so.10:   ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=3eff6de09f29e172d5d854f7903988bf49952a11, stripped
libavfilter.so.7:    ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=4c88d090d9b9f60bcc0b7562fee6b3c07fac6ff8, stripped
libavformat.so.58:   ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=8d7941a9cb888389b4b6f63921fd59297ac15ac5, stripped
libavformat.so.61:   ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=51e83dc0960be821d94a44f00540b99716639a33, stripped
libavif.so.16:       ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=2104b38d312ab7fc1c9b53270601697403a801b7, not stripped
libavresample.so.4:  ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=bfe0a37d0ab372de30c98417e0da790fe3e3217f, stripped

(this is just the first ten of many)

But! Before you get them, you need to already have the Steam client installed. Which is what you get when you install steam-installer which needs a super minimal set of 32-bit libraries to get “bootstrapped”.

You ever notice how the very first thing that happens after you launch Steam for the first time, is a massive download. Well, some of that lot above is downloaded during that step. The goal is to make sure that as soon as you open Steam, and can see your library (which you may already have on disk), you should be able to launch the games you bought today, yesterday, or a decade ago, and they should work.

I mean… this is Linux we’re talking about here, right? Just so we’re on the same page, you opened a command line prompt and typed a command to install a modern gaming store front. To paraphrase my new friend:

“That does seem a bit, erm, 1985?”

Sorry. Also, not sorry. I got my first computer in 1981 and it was 8-bit, FWIW. :smiley: It wasn’t until an IBM PS/2 Model 50Z that I got “true” 32-bit computing… Those were the days.

I agree. You got this, right?

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 steam-installer : Depends: steam-libs-i386 (= 1:1.0.0.79~ds-2) but it is not installable
E: Unable to correct problems, you have held broken packages.

If you squint, that says a lot that’s similar to what you wanted. It’s a bit more verbose, but it’s trying to help you, to be fair.

That said, in my favourite search engine if I just paste that error, verbatim steam-installer : Depends: steam-libs-i386 (= 1:1.0.0.79~ds-2) but it is not installable. This is the first result:

Guess what the first reply is. Go on, guess. :slight_smile:

Thank you x_wing! :saluting_face:

Also, I do like the profound words on their steam profile page.

“Perfecting oneself is as much unlearning as it is learning.”

Wise words, x_wing, wise words.

2 Likes

True. But then as Windows users we’ve come to expect that downloading an installer file from the web and then running it locally is the state of the art in user experiences. It’s not exactly “click on a link, go get a cup of coffee and then start browsing the list of games to play” either way.

On-

You got this, right?

Yes I did. The wall of text is pretty offputting, and the idea that “you have held broken packages” is hard to interpret. There are “broken packages”, and it’s suggesting I have taken it upon myself to “hold” them?

I did get the general gist that there was probably a 32 bit library dependency as the underlying issue, but I naively understood it was the job of the package developer and apt together to deal with dependencies (all of them). I didn’t make the leap to the fact that the 32 bit lib was a whole 'nother thing (a foreign architecture) and needed to be dealt with elsewhere.

So there you go. Maybe a nights sleep and fresh eyes might have taken me down the right Google path eventually, but the responses here helped shortcut that.

I have Steam installing as I type. It slightly offends me that it seems to install it’s libs and executables into a subdirectory of my home path (so 5 users on a machine means 5 copies of everything?) but presumably there’s a reason for that.

1 Like

Looks like you can configure storage location of games. Under Steam/Settings, select Storage, and on the top left, looks like you can change your $HOME/.steam/debian-installation… location.

5 posts were merged into an existing topic: Time to sunset the “steam-installer” deb?

5 posts were merged into an existing topic: Time to sunset the “steam-installer” deb?