Hello @Locklear93, Ubuntu inherits Debian's multi-arch requirement that architecture variants of a package must have exactly the same version to install the 32 bit and 64 bit variants together.
This is a PPA packaging issue from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa/+build/29125723 being stuck waiting on a build dependency. There's a decent chance that build would go through launchpad's build farm if a PPA package maintainer replaced pkgconf with pkg-config in [...]/debian/control. This must be evaluated and resolved on the PPA side.
As a workaround, you could inspect what package versions are available with something like apt policy libnvidia-egl-wayland1 libnvidia-egl-wayland1:i386, then tell apt to install exactly the same version for both 64 bit and 32 bit at the same time with something like sudo apt install libnvidia-egl-wayland1=<VersionChangeMe> libnvidia-egl-wayland1:i386=<SamePackageVersion>.
Closing as not a Steam client issue.
The build is still stuck and there is no installation candidate so far on Ubuntu 20.04:
apt policy libnvidia-egl-wayland1 libnvidia-egl-wayland1:i386
libnvidia-egl-wayland1:
Installed: 1:1.1.3-1ubuntu1
Candidate: 1:1.1.3-1ubuntu1
Version table:
*** 1:1.1.3-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
libnvidia-egl-wayland1:i386:
Installed: (none)
Candidate: (none)
Version table:
The probable solution is to seriously downgrade version of GPU driver, but since I use CUDA, it is not viable solution so far.
The probable solution is to seriously downgrade version of GPU driver, but since I use CUDA, it is not viable solution so far.
I directly contacted the graphics-drivers PPA maintainer after Kisak kindly explained the problem, and it was resolved within days, though I never got a reply. I was using Zorin 17, however, which is based on Ubuntu 22.04 rather than 20.04. I'm not sure if a different package is needed for focal compared to jammy.
An option for you may be to abandon Ubuntu's packaged Nvidia drivers and install directly from Nvidia's .run file. This takes more effort, but it's what I've been doing since 570. You're almost certain to need to upgrade your version of gcc to use the Nvidia installer though, as it needs to build kernel modules locally.
There's a somewhat rough tutorial on the process on Zorin's forums which should also work for Ubuntu: https://forum.zorin.com/t/how-to-install-the-latest-nvidia-driver-on-zorin-os-16-x-17-x-pop-os-21-04-24-04/42439 A link to a tutorial on updating gcc and setting the new version with update-alternatives is also included there.
During install using the Nvidia installer, it'll ask if you want to include 32-bit libraries. You do--that's precisely what's giving you trouble right now.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
After updating video drivers, Steam went from launching smoothly to complaining about dependencies. This is initially very like the terminal window that appears when Steam runs for the first time on a clean install of a distribution, stating it needs to install additional packages, and prompting the user to press return to proceed. This results in a complaint from APT that libnvidia-gl-565:i386 has an unmet dependency (libnvidia-egl-wayland1:i386), which won't be installed.
The script then prompts me to hit return to continue, and when I do, Steam starts and runs perfectly, stable for long periods, no problems observed whatsoever, implying that the file Steam thinks it needs is not needed in this case. (I have libnvidia-gl-565 and libnvidia-egl-wayland1 both installed for amd64 architecture.)
If I forcibly install libnvidia-egl-wayland1:i386 (apt install libnvidia-egl-wayland1:i386), this results in the removal of nvidia-driver-565, which of course messes things up badly on my next boot, but UNTIL that reboot, Steam stops complaining about dependencies.
I have experienced this issue twice, on two different driver versions, and once the PC is in this state, the problem persists until a full OS reinstall is performed. There's likely a less dramatic method, but I have yet to find it. The first time this occurred was on a driver update provided automatically via a system update. The second time (ongoing), happened when I manually moved from 550 to 565.
Obviously, my expected result is that if Steam is capable of running stably, it do so without prompting for installation of additional libraries and forcing me to authenticate as admin.
Steps for reproducing this issue:
Manual driver update steps: