Fedora 44 KDE can't upgrade certain packages

Ask Fedora
, ,
1

Another new issue since upgrading from FD43 to FD44 and Plasma 6.5 to Plasma 6.7

Below is the output from dnf update. Any help how to resolve these would be appreciated.

sudo dnf update --refresh
Updating and loading repositories:
 Fedora 44 - x86_64 - Updates                                                    100% | 528.0   B/s |  10.2 KiB |  00m20s
 Terra 44                                                                        100% |  74.0   B/s |   1.4 KiB |  00m19s
 RPM Fusion for Fedora 44 - Nonfree - Updates                                    100% | 304.0   B/s |   5.3 KiB |  00m18s
 RPM Fusion for Fedora 44 - Nonfree - Steam                                      100% | 333.0   B/s |   5.3 KiB |  00m16s
 RPM Fusion for Fedora 44 - Nonfree - NVIDIA Driver                              100% | 369.0   B/s |   5.5 KiB |  00m15s
 RPM Fusion for Fedora 44 - Nonfree                                              100% | 408.0   B/s |   5.7 KiB |  00m14s
 RPM Fusion for Fedora 44 - Free - Updates                                       100% | 215.0   B/s |   2.8 KiB |  00m14s
 RPM Fusion for Fedora 44 - Free                                                 100% | 243.0   B/s |   3.0 KiB |  00m13s
 google-chrome                                                                   100% | 753.0   B/s |   1.3 KiB |  00m02s
 Fedora 44 openh264 (From Cisco) - x86_64                                        100% |  82.0   B/s | 986.0   B |  00m12s
 Fedora 44 - x86_64                                                              100% |   6.2 KiB/s |  69.3 KiB |  00m11s
>>> Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-44&arch=x86_64 [Recv failure: Connection reset by peer] - https://mirrors.fedoraproject.org/metalink?repo=fedora-44&arch=x86_64
 Copr repo for PyCharm owned by phracek                                          100% |   1.2 KiB/s |   2.1 KiB |  00m02s
 Copr repo for linssid owned by nucleo                                           100% | 864.0   B/s |   1.5 KiB |  00m02s
Repositories loaded.
Problem 1: installed package libavcodec-freeworld-8.1.1-1.fc44.x86_64 conflicts with libavcodec-freeworld(x86-64) < 8.1.2 provided by libavcodec-free-8.1.2-1.fc44.x86_64 from updates
  - cannot install the best update candidate for package libavcodec-freeworld-8.1.1-1.fc44.x86_64
  - cannot install the best update candidate for package libavcodec-free-8.1.1-1.fc44.x86_64
 Problem 2: problem with installed package
  - installed package libavcodec-freeworld-8.1.1-1.fc44.x86_64 conflicts with libavcodec-freeworld(x86-64) < 8.1.2 provided by libavcodec-free-8.1.2-1.fc44.x86_64 from updates
  - package libavcodec-free-8.1.2-1.fc44.x86_64 from updates conflicts with libavcodec-freeworld(x86-64) < 8.1.2 provided by libavcodec-freeworld-8.1.1-1.fc44.x86_64 from rpmfusion-free-updates
  - package libavcodec-free-8.1.2-1.fc44.x86_64 from updates conflicts with libavcodec-freeworld(x86-64) < 8.1.2 provided by libavcodec-freeworld-8.0.1-6.fc44.x86_64 from rpmfusion-free
  - package ffmpeg-free-8.1.2-1.fc44.x86_64 from updates requires libavcodec-free(x86-64) = 8.1.2-1.fc44, but none of the providers can be installed
  - cannot install the best update candidate for package ffmpeg-free-8.1.1-1.fc44.x86_64

Package                                Arch      Version                                 Repository                  Size
Skipping packages with conflicts:
 libavcodec-free                       x86_64    8.1.2-1.fc44                            updates                 10.3 MiB
 libavcodec-freeworld                  x86_64    8.0.1-6.fc44                            rpmfusion-free          14.0 MiB
Skipping packages with broken dependencies:
 ffmpeg-free                           x86_64    8.1.2-1.fc44                            updates                  2.6 MiB

Nothing to do.
2

libavcodec-freeworld 8.1.2-1 is still in testing on rpmfusion and hasn’t been pushed to updates yet.

You can wait for it to be pushed to stable or you could run the update with rpm-fusion-free-updates-testing enabled. --enable-repo=rpmfusion-free-updates-testing

This is unrelated to the KDE updates, and sometimes happens since the packages are maintained by two different teams.

Thanks

3

Thank you for the great explanation.
I have market your reply as solution and resolved, thanks again.