Steam installation failure in Debian Sid.
Hello @CAESFIR, Debian's multiarch support requires that that architecture variants of a package must have exactly the same version to be installed beside each other. Also, Apt strongly dislikes downgrading packages to resolve conflicts.
This is a distro packaging issue, not a Steam client issue.
I would start by checking what package versions are available for libllbm19 with something like apt policy libllvm19 libllvm19:i386, then tell it to install both the 32 bit and 64 bit variants of the package at the same time with something like sudo apt install libllvm19 libllvm19:i386. This should either tell you if there's a package version mismatch with libllvm19 or give you a dependency to ponder. Repeat as needed until you find the package with the conflict.
NOTE: As a friendly reminder, you were right to not let apt uninstall a bunch of packages. At any point during troubleshooting, DO NOT let apt rip out a bunch of unexpected packages, it will give you a bad time.
Heya @kisak-valve, I used the apt policy libllvm19 libllvm19:i386 command and it tells me both amd64 and i386 share exactly the same version number.
➜ ~ sudo apt policy libllvm19 libllvm19:i386
[sudo] password for CAESFIR:
libllvm19:
Installed: 1:19.1.7-6
Candidate: 1:19.1.7-6
Version table:
*** 1:19.1.7-6 1000
1000 https://deb.debian.org/debian sid/main amd64 Packages
1000 https://mirror.xeonbd.com/debian sid/main amd64 Packages
1000 http://ftp.es.debian.org/debian sid/main amd64 Packages
1000 https://mirror.limda.net/debian sid/main amd64 Packages
100 /var/lib/dpkg/status
libllvm19:i386:
Installed: (none)
Candidate: 1:19.1.7-6
Version table:
1:19.1.7-6 1000
1000 https://deb.debian.org/debian sid/main i386 Packages
1000 https://mirror.xeonbd.com/debian sid/main i386 Packages
1000 http://ftp.es.debian.org/debian sid/main i386 Packages
1000 https://mirror.limda.net/debian sid/main i386 Packages
Additionally, when I run sudo apt install libllvm19 libllvm19:i386 command, it gives me this error
➜ ~ sudo apt install sudo apt install libllvm19 libllvm19:i386
Error: Unable to locate package install
➜ ~ sudo apt install libllvm19 libllvm19:i386
libllvm19 is already the newest version (1:19.1.7-6).
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:
libllvm19 : Conflicts: libllvm19:i386 but 1:19.1.7-6 is to be installed
libllvm19:i386 : Conflicts: libllvm19 but 1:19.1.7-6 is to be installed
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. libllvm19:i386=1:19.1.7-6 is selected for install
2. libllvm19:i386=1:19.1.7-6 is not selected for install because:
1. libllvm19:amd64 is selected for install
2. libllvm19:amd64 Conflicts libllvm19:i386
I would really appreciate if you can suggest me methods to resolve this issue!
It's odd that Apt didn't try to give any useful hints out of that. I guess I'd follow its advice and try something like sudo apt --solver 3.0 install libllvm19 libllvm19:i386.
Can you run dpkg --print-foreign-architectures and check if it tells you i386?
I'm seeing this when I type sudo apt --solver 3.0 install libllvm19 libllvm19:i386
➜ ~ sudo apt --solver 3.0 install libllvm19 libllvm19:i386
libllvm19 is already the newest version (1:19.1.7-6).
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:
libllvm19 : Conflicts: libllvm19:i386 but 1:19.1.7-6 is to be installed
libllvm19:i386 : Conflicts: libllvm19 but 1:19.1.7-6 is to be installed
Error: Unable to satisfy dependencies. Reached two conflicting decisions:
1. libllvm19:i386=1:19.1.7-6 is selected for install
2. libllvm19:i386=1:19.1.7-6 is not selected for install because:
1. libllvm19:amd64 is selected for install
2. libllvm19:amd64 Conflicts libllvm19:i386
It does show i386 when I type ➜ ~ dpkg --print-foreign-architectures
➜ ~ dpkg --print-foreign-architectures
i386
Distribution (e.g. Ubuntu): Debian Sid
This is an unstable development branch and should be expected to be broken some of the time.
If you are using sid (unstable), I would recommend also having an apt source for testing, so that you can install packages from testing when they are temporarily broken in unstable.
libllvm19 : Conflicts: libllvm19:i386 but 1:19.1.7-6 is to be installed
This is release-critical bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115227.
Workaround (untested but should work): add an apt source for testing (forky) and then do
sudo apt install libllvm19:amd64/testing libllvm19:i386/testing
As you'll see on the Debian bug report, I'm trying to help the LLVM maintainers to avoid uploading versions that regress like this in future.
Oh, interesting! That makes sense now. I really hope the maintainers patch it asap. I will meanwhile rely on testing branch for libllvm19:amd64 and libllvm19:i386 for now.
Thanks much @smcv and @kisak-valve!
You said, that I need to use testing repo? Installed fresh Debian testing, same issue.
Steam needs to install these additional packages:
libc6:amd64 libc6:i386 libegl1:amd64 libegl1:i386 libgbm1:amd64 libgbm1:i386 libgl1-mesa-dri:amd64 libgl1-mesa-dri:i386 libgl1:amd64 libgl1:i386 steam-libs-amd64:amd64 steam-libs-i386:i386
libc6 is already the newest version (2.41-12).
libegl1 is already the newest version (1.7.0-1+b2).
libegl1 is marked as manually installed.
libgbm1 is already the newest version (25.2.2-1).
libgbm1 is marked as manually installed.
libgl1-mesa-dri is already the newest version (25.2.2-1).
libgl1-mesa-dri is marked as manually installed.
libgl1 is already the newest version (1.7.0-1+b2).
Solving dependencies... Error!
Some packages cannot be installed. You may be requesting something that is not possible,
or you may be using an unstable distribution, and the packages you requested
are not yet built or have been removed from Incoming.
The following information may help you fix the situation:
Packages with unmet dependencies:
libc6:i386 : Depends: libgcc-s1:i386 but it cannot be installed
Recommends: libidn2-0:i386 (>= 2.0.5~) but it will not be installed
libegl1:i386 : Depends: libegl-mesa0:i386 but it cannot be installed
libgbm1 : Breaks: libgbm1:i386 (!= 25.2.2-1) but 25.0.7-2 will be installed
libgbm1:i386 : Depends: libdrm2:i386 (>= 2.4.121) but it cannot be installed
Depends: mesa-libgallium:i386 (= 25.0.7-2) but it cannot be installed
Breaks: libgbm1 (!= 25.0.7-2) but 25.2.2-1 will be installed
libgl1-mesa-dri : Breaks: libgl1-mesa-dri:i386 (!= 25.2.2-1) but 25.0.7-2 will be installed
libgl1-mesa-dri:i386 : Depends: libvulkan1:i386 but it cannot be installed
Depends: libgcc-s1:i386 (>= 3.0) but it cannot be installed
Breaks: libgl1-mesa-dri (!= 25.0.7-2) but 25.2.2-1 will be installed
libglx0:i386 : Depends: libglx-mesa0:i386 but it cannot be installed
libwayland-server0:i386 : Depends: libffi8:i386 (>= 3.4) but it cannot be installed
steam-libs-i386:i386 : Depends: libgcc-s1:i386 but it cannot be installed
libgcc1:i386
Depends: libgpg-error0:i386 (>= 1.10) but it cannot be installed
Depends: libstdc++6:i386 but it cannot be installed
Depends: libudev1:i386 but it will not be installed
libudev0:i386 but it will not be installed
Recommends: libasound2-plugins:i386 but it cannot be installed
Recommends: libfontconfig1:i386 but it will not be installed
Recommends: libnm0:i386 but it cannot be installed
Recommends: libxkbcommon-x11-0:i386 but it will not be installed
Recommends: libva-drm2:i386 but it cannot be installed
Recommends: libva-glx2:i386 but it cannot be installed
Recommends: libva-x11-2:i386 but it cannot be installed
Recommends: mesa-vulkan-drivers:i386 but it cannot be installed
Recommends: va-driver-all:i386 but it cannot be installed
va-driver:i386
E: Unable to fix the problem, you have broken fixed packages.
E: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. libgbm1:amd64=25.2.2-1 is selected for installation because:
1. libgbm1:amd64 is selected for installation
2. libgbm1:amd64 is available in versions 25.2.2-1, 25.0.7-2
[selected libgbm1:amd64]
For context, additional options that could not be installed:
* In libgbm1:amd64 is available in versions 25.2.2-1, 25.0.7-2:
- libgbm1:amd64=25.0.7-2 is not selected for installation
2. libgbm1:amd64=25.2.2-1 is not selected for installation because:
1. libgbm1:i386=25.0.7-2 is selected for installation
2. libgbm1:amd64=25.2.2-1 Breaks libgbm1:i386 (!= 25.2.2-1)
Hi @marshallovski, I resolved the issue by specifically pinning libllvm19:amd64 and libllvm19:i386 packages with high enough priority to use testing repository, while my entire system continues using Debian sid / unstable.
I'm using this as a temporary fix until the libllvm19 package gets updated to fix the issue in Debian Sid. Since I am currently having issues installing another package due to the lower version of libllvm19, specifically, ProtonVPN.
I think the issue you are having has to do with something else than libllvm19, since I see multiple versions of same packages present in the log you posted. Perhaps you have multiple repositories with same priority enabled?
I resolved the issue by specifically pinning libllvm19:amd64 and libllvm19:i386 packages with high enough priority to use testing repository, while my entire system continues using Debian sid / unstable
Yes, this is a good way to work around problems with unstable.
Hi @marshallovski, I resolved the issue by specifically pinning libllvm19:amd64 and libllvm19:i386 packages with high enough priority to use testing repository, while my entire system continues using Debian sid / unstable. I'm using this as a temporary fix until the libllvm19 package gets updated to fix the issue in Debian Sid. Since I am currently having issues installing another package due to the lower version of libllvm19, specifically, ProtonVPN.
I think the issue you are having has to do with something else than libllvm19, since I see multiple versions of same packages present in the log you posted. Perhaps you have multiple repositories with same priority enabled?
These are my sources:
Heya @marshallovski, Trixie moved to stable last month, Forky is testing now.
Try enabling all components, including contrib and non-free, you already have main and non-free-firmware, but steam requires packages from the other two as well.
Additionally, could you do dpkg --print-foreign-architectures and see if it shows i386, if not, do sudo dpkg --add-architecture i386 and then sudo apt update.
Try launching Steam afterwards.
For easier readability of sources, you could also do sudo apt modernize-sources, your sources will move to /etc/apt/sources.list.d/ by doing so. E.g. /etc/apt/sources.list.d/debian.sources
Make sure debian.sources's Components has all four present main contrib non-free non-free-firmware
debian.sources in /etc/apt/sources.list.d/ should look something like this:
Types: deb deb-src
URIs: https://deb.debian.org/debian
Suites: trixie trixie-updates trixie-backports
Components: main contrib non-free non-free-firmware
Architectures: amd64 i386
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Types: deb deb-src
URIs: https://security.debian.org/debian-security
Suites: trixie-security
Components: main contrib non-free non-free-firmware
Architectures: amd64 i386
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
This is release-critical bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115227.
This was fixed in llvm-toolchain-19 version 1:19.1.7-7, which was uploaded today but might not be available on your mirror yet.
There is additional test coverage to try to stop this happening again, but in general, similar installability issues with Debian unstable can usually be resolved by temporarily taking the relevant packages from Debian testing.
I think the issue you are having has to do with something else than libllvm19, since I see multiple versions of same packages present in the log you posted
Yes, the different issue described by @marshallovski does not seem to be related to libllvm19. Instead, it looks like an attempt to install i386 packages from Debian 13 (stable) while amd64 packages newer than that are already installed. Debian's support for installing amd64 and i386 packages together is very dependent on those packages being consistent with each other.
Nothing extracted yet.
Your system information
1.0.0.84
Debian Sid
Yes
Yes
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]steam-logs.tar.gz
Nvidia GTX 1660 Super
Please describe your issue in as much detail as possible:
This is what I see when launching steam.
https://gist.github.com/CAESFIR/571f1cca6749e050e2ae9655cb08aab8
Steam never boots, it says I have conflicting packages, however the problem is if I try to install libllvm19:i386, it tells me it will remove pretty much everything from my pc.
Also note, this is a complete fresh install of Debian Sid - I had to reinstall it twice because it kept giving me the same error as now, which I assumed had something to do with a mistake I made.
The following packages have unmet dependencies:
mesa-libgallium:i386 : Depends: libllvm19:i386 (>= 1:19.1.0) but it is not installable
E: Unable to correct problems, you have held broken packages.
E: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
Steps for reproducing this issue: