Hi,
I have a nvidia dnf versionlock to make sure the drivers don’t update to 590. This work as intended when doing dnf update, however Discover updates disregards this versionlock.
This may be because Discover is using the old version of dnf and not the new dnf5.
This is the case on Fedora 43 for example, which I think is due to be fixed on f44.
Which distro and version are you using?
I’m using Fedora 42 with KDE Plasma Version: 6.5.5 on Kernel 6.16.7-200 for Wayland.
While writing and testing I came to this final answer:
**Bug 2026184 - PackageKit does not respect `dnf versionlock`
”**https://github.com/PackageKit/PackageKit/issues/444”
Thank you,
Let’s try:
sudo dnf install python3-dnf-plugin-versionlock
sudo dnf4 versionlock \*nvidia\*585\*
sudo dnf4 update –-refresh
sudo dnf-3 versionlock \*nvidia\*585\*
Package already locked in equivalent form: …
Seems dnf-3 is just a link to dnf4.
Discover still wants to update my nvidia drivers to version 590.
So i Duck it and
Duck a.i. says:
“KDE Discover does not use a specific version of DNF; instead, it relies on the DNF package manager installed on your system”
fedora discussions says:
“PackageKit backend for Discover is still on dnf3”
”Dnf-3 has been a link to dnf4 for many years.”
And then it hits:
Bug 2026184 - PackageKit does not respect `dnf versionlock` (from 2021)
Personally I use dnf to do updates and not Discover.
When dnf is used issues are easy to debug as there is output with enough info to allow for an understanding of what dnf is doing or failing to do.
I also favor dnf and compiling my kernel and all packages myself, but why have discover - updates then? (It’s not true. I have not the balls and knowhow to even attempt doing this.) 
But like you said, packagekit will get dnf5 backend at some point, with versionlock support.
It will have taken 6 years (ykne opened on Nov 23, 2020) to get to a fix. Hoera for Fedora 44. 
Why? For people that like GUIs and prefer to avoid the command line I think.
Personally I unistall Discover and PackageKit.
I feel you didn’t get my joke. 
^^ I personally like to edit/inject the electrons directly to my monitor’s pixels to bypass the cpu, firmware and buggy software. No electricity or debugging needed and you always see the result you wanted. 