Issues with F40 -> F41 Upgrade - Software Center

Used Discover to upgrade to 41. Was surprised to not see a 41 kernel option on grub, is that expected? The system reboots but the Software Center wants to Install F41 System software and all installed apps.

  1. Download fails with:
file /usr/share/man/man5/dnf.conf.5.gz from install of dnf5-5.2.6.2-1.fc41.x86_64 conflicts with file from package dnf-data-4.21.1-1.fc40.noarch
file /usr/share/doc/libffi/README.md from install of libffi-3.4.6-3.fc41.i686 conflicts with file from package libffi-3.4.4-7.fc40.x86_64
file /usr/share/licenses/libffi/LICENSE from install of libffi-3.4.6-3.fc41.i686 conflicts with file from package libffi-3.4.4-7.fc40.x86_64
file /usr/share/doc/fribidi/ChangeLog from install of fribidi-1.0.15-2.fc41.i686 conflicts with file from package fribidi-1.0.14-2.fc40.x86_64
file /usr/share/doc/fribidi/NEWS from install of fribidi-1.0.15-2.fc41.i686 conflicts with file from package fribidi-1.0.14-2.fc40.x86_64
file /usr/share/licenses/xz-libs/COPYING from install of xz-libs-1:5.6.2-2.fc41.i686 conflicts with file from package xz-libs-1:5.4.6-3.fc40.x86_64
file /usr/share/doc/gmp/NEWS from install of gmp-1:6.3.0-2.fc41.i686 conflicts with file from package gmp-1:6.2.1-8.fc40.x86_64
file /usr/share/man/man1/trust.1.gz from install of p11-kit-0.25.5-3.fc41.i686 conflicts with file from package p11-kit-0.25.5-1.fc40.x86_64
file /usr/share/man/man5/pkcs11.conf.5.gz from install of p11-kit-0.25.5-3.fc41.i686 conflicts with file from package p11-kit-0.25.5-1.fc40.x86_64 .....
TL:DR
  1. dnf update reports Nothing to do.
  2. uname -r reports: 6.11.6-200.fc40.x86_64
  3. hostnamectl reports:
             Chassis: desktop šŸ–„ļø
          Machine ID: 8883037563724a9196e6d5fb8bdddc34
             Boot ID: 093ed0c2c8f347068260d3c60fe588e9
    Operating System: Fedora Linux 41 (Workstation Edition)
         CPE OS Name: cpe:/o:fedoraproject:fedora:41
      OS Support End: Mon 2025-12-15
OS Support Remaining: 1y 1month 2d                         
              Kernel: Linux 6.11.6-200.fc40.x86_64
        Architecture: x86-64
     Hardware Vendor: SYWZ
      Hardware Model: S210H Series
    Firmware Version: 5.17
       Firmware Date: Wed 2021-09-01
        Firmware Age: 3y 2month 1w 4d 

Do I have any options to recover and is there a Discover log file that I can review?

From a terminal try sudo dnf distro-sync --releasever=41

I ran sudo dnf remove \*i686 as suggested in another post, now Discover only reports:

Error running transaction: file /etc/dnf/dnf.conf from install of libdnf5-5.2.6.2-1.fc41.x86_64 conflicts with file from package dnf-data-4.21.1-1.fc40.noarch
file /usr/share/man/man5/dnf.conf.5.gz from install of dnf5-5.2.6.2-1.fc41.x86_64 conflicts with file from package dnf-data-4.21.1-1.fc40.noarch

I ran sudo dnf distro-sync --releasever=41 and got:

Error: 
 Problem: problem with installed package docker-compose-plugin-2.29.7-1.fc40.x86_64
  - package docker-compose-2.29.7-1.fc41.x86_64 from fedora conflicts with docker-compose-plugin provided by docker-compose-plugin-2.29.2-1.fc41.x86_64 from docker-ce-stable
  - package docker-compose-2.29.7-1.fc41.x86_64 from fedora conflicts with docker-compose-plugin provided by docker-compose-plugin-2.29.6-1.fc41.x86_64 from docker-ce-stable
  - package docker-compose-2.29.7-1.fc41.x86_64 from fedora conflicts with docker-compose-plugin provided by docker-compose-plugin-2.29.7-1.fc41.x86_64 from docker-ce-stable
  - problem with installed package docker-compose-1.29.2-12.fc40.noarch
  - package docker-compose-2.29.7-3.fc41.x86_64 from updates conflicts with docker-compose-plugin provided by docker-compose-plugin-2.29.2-1.fc41.x86_64 from docker-ce-stable
  - package docker-compose-2.29.7-3.fc41.x86_64 from updates conflicts with docker-compose-plugin provided by docker-compose-plugin-2.29.6-1.fc41.x86_64 from docker-ce-stable
  - package docker-compose-2.29.7-3.fc41.x86_64 from updates conflicts with docker-compose-plugin provided by docker-compose-plugin-2.29.7-1.fc41.x86_64 from docker-ce-stable
  - docker-compose-plugin-2.29.7-1.fc40.x86_64 from @System  does not belong to a distupgrade repository
  - docker-compose-1.29.2-12.fc40.noarch from @System  does not belong to a distupgrade repository
(try to add '--allowerasing' to command line to replace conflicting packages)

Tried with --skip-broken and --allowerasing

Now if I run sudo dnf update it wants to downgrade some packages:

Upgrading:
 libxcrypt                      x86_64          4.4.36-10.fc40           updates                   119 k
     replacing  libxcrypt.x86_64 4.4.36-8.fc41
 libxcrypt-compat               x86_64          4.4.36-10.fc40           updates                    90 k
     replacing  libxcrypt-compat.x86_64 4.4.36-8.fc41
 libxcrypt-devel                x86_64          4.4.36-10.fc40           updates                    29 k
     replacing  libxcrypt-devel.x86_64 4.4.36-8.fc41
 pyproject-srpm-macros          noarch          1.16.0-1.fc40            updates                    14 k
     replacing  pyproject-srpm-macros.noarch 1.15.1-1.fc41
 python3-boto3                  noarch          1.35.55-1.fc40           updates                   397 k
 python3-botocore               noarch          1.35.55-1.fc40           updates                   7.3 M
 rhino                          noarch          1.7.14-13.fc40           updates                   1.3 M
 vamp-plugin-sdk                x86_64          2.10-2.fc40              updates                   178 k
     replacing  vamp-plugin-sdk.x86_64 2.10-1.fc41
 xorg-x11-server-Xorg           x86_64          1.20.14-36.fc40          updates                   1.5 M
 zenity     

Docker-compose seems to have an issue with the packages you have installed at the moment.

$ sudo dnf list docker-compose docker-compose-plugin
Updating and loading repositories:
Repositories loaded.
Available packages
docker-compose.x86_64 2.29.7-3.fc41 updates
docker-compose.x86_64 2.29.7-3.fc41 updates-archive

Note that docker-compose-plugin is not shown in the f41 results so docker-compose cannot be upgraded.

If you remove ā€˜docker-compose-pluginā€™ the upgrade would probably work.

Note that the downgrade is replacing f40 packages with the current f41 packages.

I let the downgrade execute and rebooted but I still canā€™t get Discover to work:

Error running transaction: file /etc/dnf/dnf.conf from install of libdnf5-5.2.6.2-1.fc41.x86_64 conflicts with file from package dnf-data-4.21.1-1.fc40.noarch
file /usr/share/man/man5/dnf.conf.5.gz from install of dnf5-5.2.6.2-1.fc41.x86_64 conflicts with file from package dnf-data-4.21.1-1.fc40.noarch

It appears all of the libraries/packages are duplicated:

Box2D-0:2.4.2-1.fc40.x86_64
Box2D-0:2.4.2-1.fc41.x86_64
GConf2-0:3.2.6-41.fc40.x86_64
GConf2-0:3.2.6-42.fc41.x86_64
GraphicsMagick-0:1.3.40-7.fc40.x86_64
GraphicsMagick-0:1.3.45-1.fc41.x86_64
GraphicsMagick-c++-0:1.3.40-7.fc40.x86_64
GraphicsMagick-c++-0:1.3.45-1.fc41.x86_64
LibRaw-0:0.21.3-1.fc40.x86_64
LibRaw-0:0.21.3-1.fc41.x86_64
ModemManager-0:1.22.0-3.fc40.x86_64
ModemManager-0:1.22.0-4.fc41.x86_64
ModemManager-glib-0:1.22.0-3.fc40.x86_64
ModemManager-glib-0:1.22.0-4.fc41.x86_64
NetworkManager-1:1.46.2-1.fc40.x86_64
NetworkManager-1:1.50.0-1.fc41.x86_64
NetworkManager-libnm-1:1.46.2-1.fc40.x86_64
NetworkManager-libnm-1:1.50.0-1.fc41.x86_64
NetworkManager-openconnect-0:1.2.10-5.fc40.x86_64
NetworkManager-openconnect-0:1.2.10-6.fc41.x86_64
NetworkManager-openvpn-1:1.12.0-1.fc40.x86_64
NetworkManager-openvpn-1:1.12.0-2.fc41.x86_64 ..... etc

How do I tell which packages/libraries are being used?

Currently getting on Discover/Software update:


Failed to install updates: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.PackageKit': activation request failed: unit is invalid

I finally got my upgrade to 41 to work. Basically by doing the initial upgrade using the software center used dnf4(I think) and fails leaving a whole lot of broken stuff.

  1. Manually installed dnf5
  2. Ran sudo dnf5 distro-sync --releasever=41
  3. Got into the reported login loop issue(also tried most of the suggested solutions)
  4. Fixed all of the selinux problem(18)
  5. rebooted
    Wow - there seems to be a cleaner way to get to dnf5.