Trying to install the latest update results in this error
Dependency resolution failed:The following packages have unmet dependencies:
linux-modules-nvidia-580-open-6.14.0-32-generic: Depends: nvidia-kernel-common-580 (<= 580.65.06-1) but 580.95.05-0ubuntu0.24.04.2 is to be installed
I’m not sure if this should be classified as a bug so I posted here first.
Can you step us through the exact process used to install the driver. I’m running the 580.95.05 drivers here and the latest KDE Neon update went through just fine.
I used ubuntu-drivers.
I’ve used the Nvidia Launchpad PPA since it’s release and I’ve never encountered an issue. Perhaps try uninstalling the drivers, adding the Launchpad PPA, and installing the drivers via the Launchpad PPA:
Apparently I have a situation that apt can handle but pkcon can not.
apt output
❯ sudo apt full-upgrade
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) linux-modules-nvidia-580-open-6.14.0-32-generic:amd64 < 6.14.0-32.32~24.04.1+1 @ii mK Ib >
Broken linux-modules-nvidia-580-open-6.14.0-32-generic:amd64 Depends on nvidia-kernel-common-580:amd64 < 580.65.06-0ubuntu0.24.04.4 → 580.95.05-0ubuntu0.24.04.2 @ii umU > (<= 580.65.06-1)
Considering nvidia-kernel-common-580:amd64 18 as a solution to linux-modules-nvidia-580-open-6.14.0-32-generic:amd64 0
Removing linux-modules-nvidia-580-open-6.14.0-32-generic:amd64 rather than change nvidia-kernel-common-580:amd64
Done
Entering ResolveByKeep
Calculating upgrade… Done
The following package was automatically installed and is no longer required:
nvidia-firmware-580-580.65.06
Use ‘sudo apt autoremove’ to remove it.
The following packages will be REMOVED:
linux-modules-nvidia-580-open-6.14.0-32-generic
The following NEW packages will be installed:
nvidia-firmware-580-580.95.05
The following packages will be upgraded:
bluez bluez-cups bluez-obexd libbluetooth3 libnvidia-cfg1-580 libnvidia-common-580 libnvidia-compute-580 libnvidia-decode-580
libnvidia-encode-580 libnvidia-extra-580 libnvidia-fbc1-580 libnvidia-gl-580 linux-modules-nvidia-580-open-6.14.0-33-generic
linux-modules-nvidia-580-open-generic-hwe-24.04 nvidia-compute-utils-580 nvidia-dkms-580-open nvidia-driver-580-open
nvidia-kernel-common-580 nvidia-kernel-source-580-open nvidia-utils-580 xserver-xorg-video-nvidia-580
21 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 332 MB of archives.
After this operation, 94.9 MB of additional disk space will be used.
Do you want to continue? [Y/n]
pkcon output:
❯ sudo pkcon update
Getting updates [=========================]
Finished [=========================]
Loading cache [=========================]
Testing changes [=========================]
Finished [=========================]
Fatal error: The following packages have unmet dependencies:
linux-modules-nvidia-580-open-6.14.0-32-generic: Depends: nvidia-kernel-common-580 (<= 580.65.06-1) but 580.95.05-0ubuntu0.24.04.2 is to be installed
You’re drawing from Canonical repo’s when installing Nvidia drivers, however I believe that pkcon by default is configured to ignore Canonical repo’s due to the fact KDE Neon is based on Ubuntu LTS, but is actually a Frankenstein of Ubuntu LTS due to the fact that it’s running a rolling Plasma DE, and dependency issues can be a problem if you install software from Canonical’s repo’s (as I think you’ve discovered).
I don’t encounter the issue as I’m drawing from the Nvidia Launchpad PPA and not Canonical’s repo’s for Nvidia drivers.
Honestly? I’ve been using KDE Neon as a loyal user since 2018; but this situation with apt, pkcon and the installation of software is getting on my nerves. As a result, a few months ago I set up a secondary PC with CachyOS running Plasma 6.4.5 and set it up identical to my KDE Neon based main PC for testing - Using paru, software installation is a breeze, and should I have a problem I can restore a previous snapshot either via GRUB or using BTRFS Assistant faster than it takes to say ‘snapshot’. I plan to install a second m.2 4TB SSD to supplement my existing 1TB m.2 nvme SSD, and I plan on installing a new 8TB storage HDD to replace my current 6TB storage HDD; when I do so I will be dumping KDE Neon in favor of CachyOS - CachyOS really is that good.
And the best thing? No more Nvidia driver issues as they’re compiled along with OS updates by CachyOS devs. Unlike KDE Neon, you’re not being told ‘we only support AMD hardware, should you use Nvidia hardware there be Dragons’.
Under CachyOS running Nvidia drivers/hardware, I can even suspend to ram and wake from suspend perfectly, I never turn this secondary PC off and I use it as much as I use my main PC. In comparison, KDE Neon will not wake from suspend to ram no matter how hard I try.
Hah. Interesting. Since ubuntu-drivers was included I just assumed that was the proper, stable way to install the Nvidia drivers on Neon. I might give the PPA a shot if I can’t sort it out some other way.
I’ve been using the Launchpad PPA since before I switched to KDE Neon in 2018, so naturally I’ve been using it for as long as I’ve been running KDE Neon - And in all that time I have never experienced a single issue with drivers or dependency issues.
However, as stated, KDE Neon is not strictly an Ubuntu LTS based distro due to the fact it’s running a rolling Plasma DE - So while I haven’t experienced any issues running the Launchpad PPA to date, that’s not to say they aren’t possible. KDE devs tiptoe around the issue, stating that they only support the open Nouveau driver when it comes to Nvidia hardware - But the fact remains that from an outright performance perspective especially under anything from Turing onwards - Nouveau is really only useful for installing the Nvidia proprietary drivers.
Well, everything seems fine after apt full-upgradde so this is more of a small annoyance than an actual problem. Just gotta remember this the next time it happens.
Bear in mind, this can happen any time you use apt to install software. This isn’t an issue limited to just Nvidia drivers. Furthermore, using apt to resolve dependency issues resulting from installing software via apt can actually result in further dependency issues under KDE Neon for the reasons mentioned in my previous post.
No, it does not do that at all.
I’ve noted a Kubuntu user with the same error, and maybe one other *buntu user.
I can’t verify or check recent updates, but when pkcon or Discover has a different result like this, it can be from Ubuntu having packages being phased. This is sort of randomized, and I’ve seen a Discover or pkcon session being phased while apt isn’t, and vice versa.
There have been some packages being phased this week, and if one of those were a dependency for a driver package, this could be a cause for this problem. Just a theory, though I have seen similar things myself in the past as well as other user reports.
The problem is, pkcon hides much of the output when it runs apt, so the actual blockers are not always seen. I see bluez is still phased for some (including me atm) but I know there were others as well. Odd as it may seem, the onion layers of dependencies might connect this to Nvidia packages.
To be honest, the original reasons for …suggesting pkcon and the fairly recent addition of not having “support” for Nvidia is sort of a protection or caveat for new or unfamiliar users.
Imnsho of course, as well as observations and discussions.
Well, this is where the lines blur regarding KDE Neon, because technically KDE Neon is ‘based’ on Ubuntu LTS, but it is not an official Ubuntu LTS flavor, and therefore has to rely on it’s own repo’s for it’s rolling KDE DE that uses packages that aren’t inline with distro’s based on official Ubuntu LTS releases.
This was actually a point of contention in the '“Wine is essential for many of us” thread:
To quote the KDE Neon FAQ page:
How do I Update to the Latest Software?
KDE neon does continuous deployment of the latest KDE software which means there are nearly always new versions of our software to update to. We recommend using Plasma Discover’s updater which appears in your panel:
If you prefer to use the command line you can use the pkcon command:
pkcon refresh
pkcon updateThis will install all new packages and uses the same PackageKit code as Plasma Discover. Some uses of
aptdo not install new packages which makes it less suitable for KDE neon.
This happened to me. It seems there are some transitional packages that were broken. What I did was purge the existing driver
sudo apt remove --purge ‘^nvidia-.*’
Then reboot, which should bring you into Nouveau. It might take a minute or two to configure itself. Then I just reinstalled the driver:
sudo ubuntu-drivers install nvidia-driver-580
Then reboot again.
Have not had any issues since.
Happening to me just today:
Dependency resolution failed:can I just wait to understand if next release will solve the problem? Not very skilled in sysadmin, I’m more a end user that look at help from AI or more experienced users about what to do, so didn’t want to touch anything without a reason.
This problem happens for me on Kubuntu almost every time there is an nVidia update. Last time, I fixed it with:
sudo ubuntu-drivers autoinstall
Honestly, I use the Launchpad PPA, and I’ve never encountered a single issue in the many, many years I’ve been using it.
This solved my problem, thanks
Glad it worked for you too.