Sorry, I can’t seem to post the full output, but here are the problems listed at the beginning. I ran sudo dnf update.
Problem 1: cannot install the best update candidate for package libkworkspace6-6.1.5-1.fc40.x86_64
- nothing provides plasma-workspace-common = 6.2.0-2.fc40 needed by libkworkspace6-6.2.0-2.fc40.x86_64 from updates-archive
Problem 2: cannot install the best update candidate for package plasma-workspace-6.1.5-1.fc40.x86_64
- nothing provides plasma-workspace-common = 6.2.0-2.fc40 needed by plasma-workspace-6.2.0-2.fc40.x86_64 from updates-archive
- nothing provides plasma-workspace-wayland = 6.2.0-2.fc40 needed by plasma-workspace-6.2.0-2.fc40.x86_64 from updates-archive
Problem 3: cannot install the best update candidate for package plasma-workspace-libs-6.1.5-1.fc40.x86_64
- nothing provides plasma-workspace-common = 6.2.0-2.fc40 needed by plasma-workspace-libs-6.2.0-2.fc40.x86_64 from updates-archive
Problem 4: package sddm-breeze-6.2.0-1.fc40.noarch from updates-archive requires plasma-workspace >= 6.2, but none of the providers can be installed
- cannot install the best update candidate for package sddm-breeze-6.1.5-1.fc40.noarch
- nothing provides plasma-workspace-common = 6.2.0-2.fc40 needed by plasma-workspace-6.2.0-2.fc40.x86_64 from updates-archive
- nothing provides plasma-workspace-wayland = 6.2.0-2.fc40 needed by plasma-workspace-6.2.0-2.fc40.x86_64 from updates-archive
Problem 5: package plasma-workspace-x11-6.2.0-2.fc40.x86_64 from updates-archive requires plasma-workspace = 6.2.0, but none of the providers can be installed
- cannot install the best update candidate for package plasma-workspace-x11-6.1.5-1.fc40.x86_64
- nothing provides plasma-workspace-common = 6.2.0-2.fc40 needed by plasma-workspace-6.2.0-2.fc40.x86_64 from updates-archive
- nothing provides plasma-workspace-wayland = 6.2.0-2.fc40 needed by plasma-workspace-6.2.0-2.fc40.x86_64 from updates-archive
Problem 6: package plasma-lookandfeel-fedora-6.2.0-2.fc40.noarch from updates-archive requires plasma-workspace = 6.2.0-2.fc40, but none of the providers can be installed
- cannot install the best update candidate for package plasma-lookandfeel-fedora-6.1.5-1.fc40.noarch
- nothing provides plasma-workspace-common = 6.2.0-2.fc40 needed by plasma-workspace-6.2.0-2.fc40.x86_64 from updates-archive
- nothing provides plasma-workspace-wayland = 6.2.0-2.fc40 needed by plasma-workspace-6.2.0-2.fc40.x86_64 from updates-archive
Problem 7: package kde-cli-tools-6.2.0-1.fc40.x86_64 from updates-archive requires libkworkspace6(x86-64) >= 6.2.0, but none of the providers can be installed
- cannot install the best update candidate for package kde-cli-tools-6.1.5-1.fc40.x86_64
- nothing provides plasma-workspace-common = 6.2.0-2.fc40 needed by libkworkspace6-6.2.0-2.fc40.x86_64 from updates-archive
Problem 8: package plasma-desktop-6.2.0-1.fc40.x86_64 from updates-archive requires kde-cli-tools, but none of the providers can be installed
- package kde-cli-tools-6.1.5-1.fc40.x86_64 from @System requires kdesu = 1:6.1.5-1.fc40, but none of the providers can be installed
- package kde-cli-tools-6.1.5-1.fc40.i686 from updates requires kdesu = 1:6.1.5-1.fc40, but none of the providers can be installed
- package kde-cli-tools-6.1.5-1.fc40.x86_64 from updates requires kdesu = 1:6.1.5-1.fc40, but none of the providers can be installed
- package kde-cli-tools-6.1.5-1.fc40.x86_64 from updates-archive requires kdesu = 1:6.1.5-1.fc40, but none of the providers can be installed
- package kde-cli-tools-6.0.3-1.fc40.i686 from fedora requires kdesu = 1:6.0.3-1.fc40, but none of the providers can be installed
- package kde-cli-tools-6.0.3-1.fc40.x86_64 from fedora requires kdesu = 1:6.0.3-1.fc40, but none of the providers can be installed
- package kde-cli-tools-6.0.4-1.fc40.x86_64 from updates-archive requires kdesu = 1:6.0.4-1.fc40, but none of the providers can be installed
- package kde-cli-tools-6.1.0-1.fc40.x86_64 from updates-archive requires kdesu = 1:6.1.0-1.fc40, but none of the providers can be installed
- package kde-cli-tools-6.1.1-1.fc40.x86_64 from updates-archive requires kdesu = 1:6.1.1-1.fc40, but none of the providers can be installed
- package kde-cli-tools-6.1.3-2.fc40.x86_64 from updates-archive requires kdesu = 1:6.1.3-2.fc40, but none of the providers can be installed
- package kde-cli-tools-6.1.4-1.fc40.x86_64 from updates-archive requires kdesu = 1:6.1.4-1.fc40, but none of the providers can be installed
- cannot install both kdesu-1:6.2.0-1.fc40.x86_64 from updates-archive and kdesu-1:6.1.5-1.fc40.x86_64 from @System
- cannot install both kdesu-1:6.2.0-1.fc40.x86_64 from updates-archive and kdesu-1:6.0.3-1.fc40.x86_64 from fedora
- cannot install both kdesu-1:6.2.0-1.fc40.x86_64 from updates-archive and kdesu-1:6.1.5-1.fc40.x86_64 from updates
- cannot install both kdesu-1:6.2.0-1.fc40.x86_64 from updates-archive and kdesu-1:6.0.4-1.fc40.x86_64 from updates-archive
- cannot install both kdesu-1:6.2.0-1.fc40.x86_64 from updates-archive and kdesu-1:6.1.0-1.fc40.x86_64 from updates-archive
- cannot install both kdesu-1:6.2.0-1.fc40.x86_64 from updates-archive and kdesu-1:6.1.1-1.fc40.x86_64 from updates-archive
- cannot install both kdesu-1:6.2.0-1.fc40.x86_64 from updates-archive and kdesu-1:6.1.3-2.fc40.x86_64 from updates-archive
- cannot install both kdesu-1:6.2.0-1.fc40.x86_64 from updates-archive and kdesu-1:6.1.4-1.fc40.x86_64 from updates-archive
- cannot install both kdesu-1:6.2.0-1.fc40.x86_64 from updates-archive and kdesu-1:6.1.5-1.fc40.x86_64 from updates-archive
- package kde-cli-tools-6.2.0-1.fc40.x86_64 from updates-archive requires libkworkspace6(x86-64) >= 6.2.0, but none of the providers can be installed
- cannot install the best update candidate for package plasma-desktop-6.1.5-1.fc40.x86_64
- cannot install the best update candidate for package kdesu-1:6.1.5-1.fc40.x86_64
- nothing provides plasma-workspace-common = 6.2.0-2.fc40 needed by libkworkspace6-6.2.0-2.fc40.x86_64 from updates-archive
# This is a repo that contains all the old update packages from the
# Fedora updates yum repository (i.e. the packages that have made it
# to "stable"). This repo is needed for OSTree based systems where users
# may be trying to layer packages on top of a base layer that doesn't
# have the latest stable content. Since base layer content is locked
# the package layering operation will fail unless there are older versions
# of packages available.
#
# This repo is given a high cost in order to prefer the normal Fedora
# yum repositories, which means only packages that can't be found
# elsewhere will be downloaded from here.
[updates-archive]
name=Fedora $releasever - $basearch - Updates Archive
baseurl=https://fedoraproject-updates-archive.fedoraproject.org/fedora/$releasever/$basearch/
enabled=1
metadata_expire=6h
repo_gpgcheck=0
type=rpm
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=True
cost=10000 # default is 1000
So that’s what “updates-archive” is, so why use that? The repo comment section does mention OSTree which I don’t have any background in (silverblue).
Likely not his choice.
I see the same repo enabled on my system and I can confirm that I did not manually enable it. Apparently at some point an update enabled that repo for F40. I am using Workstation so not an ostree system.
Yeah, that’s what I always use. I’d just already done a refresh several times. It ended up working some hours later. I think I even ran dnf clean all && dnf --refresh check-update.
QEMU, clamav and xorg-x11-server-Xwayland are things I installed personally, I think. I’m using regular Fedora 40 KDE. What do you have from that repo?
I am using Workstation and have never installed anything from that archive.
Using the same exact command you show I see nothing in the list.
I have qemu packages from updates that are the same version.
In fact, with every package I compared of what you show and I also have, I see an identical version installed directly from updates and not from updates-archive.
One thing to note for future reference.
It seems that once a package is installed from a particular repo the system tends to rely on that repo for updates. I see this with the nvidia drivers, where the rpmfusion-nonfree-nvidia-driver repo may have one version and the rpmfusion-nonfree repo has a different version of the same package. Even with both repos enabled, when the packages are installed from the repo with the lower version an update does not automatically pull in the updated package from the other repo.