F43 WRK-> F44 upgrade report

Upgraded my main system ( WRK, 6.19.9 + nvidia rpmfusion style 595.45.04) yesterday from F43 to F44 and it went smoothly with only a minor issue with one app that required some attention.

Unlike the last upgrade from f42 to f43, the ‘dnf offline reboot’ step completed without any errors. Just in case, I’ve since set a PW for the root account and unlocked it! :slight_smile:

akmods compiled the ndivia driver modules on first boot. :+1:

pulled some updates from updates-testing (gnome-50, ibus, and other stuff that I already had installed on f43)

here are a few observations worth mentioning

  1. had to use option --allowerasing because of package igt-gpu-tools
    turns out this package can’t be reinstalled in f44 either, because it still has a dependency on libproc2.so.0. 2436237 – F44FailsToInstall: igt-gpu-tools

  2. "for some reason the upgraded system reports the repositories used for the upgrade (fedora) as <unknown>.

$ dnf list --installed fedora-release\*
Installed packages (available for reinstall, available for upgrade)
fedora-release-common.noarch               44-0.15 <unknown>
fedora-release-identity-workstation.noarch 44-0.15 <unknown>
fedora-release-workstation.noarch          44-0.15 <unknown>

this is the output of dnf system-upgrade download --releasever 44

 fedora-release-common                            noarch 44-0.15    fedora
   replacing fedora-release-common                noarch 43-26      updates
 fedora-release-identity-workstation              noarch 44-0.15    fedora
   replacing fedora-release-identity-workstation  noarch 43-26      updates
 fedora-release-workstation                       noarch 44-0.15    fedora
   replacing fedora-release-workstation           noarch 43-26      updates 
  1. several gnome-shell extensions have been disabled
    adding “50” to the metadata.json for caffeine and system-monitor-next has fixed that.
    Other disabled extensions are Dash to Panel, Just Perfection, Pop Shell. I don’t use them and did not check if the same simple edit would fix those.

  2. Audacious refused playing https streams e.g. BFBS Edge. Error was something like can’t verify … (forgot to take note if the the error message)
    for some reason this can’t be reproduced in a new VM or with my rescue/test system on an external SSD ( original install F41). The fix seems to be
    sudo ca-legacy install sudo ca-legacy default
    Original install was F38, and upgraded since with every version to F44. So there may be something worth looking into for system that were installed originally with F40 and older.
    VLC or deadbeef were not affected.

UPDATE: turns out it is reproducible with any current f43->f44 upgrade. For some reason f42 → f44 upgrade is not affected!.
Installed f43 WRK VM with the f43-everything.iso and upgraded to f44.

  1. the most annoying thing is that default change for the middle mouse button! Set it to enabled if the previous setting was still default! Change it to default if the previous setting was expl. disabled!

Other then that there is nothing no complain! :slight_smile:
Everything works w/o issue so far. Kudos to everyone involved!

1 Like

This is because you apparently used packagekit [gnome software] (which uses dnf4 for its operations) to perform the upgrade. The command line dnf is dnf5 and packagekit uses dnf4. There are different cache locations for each and dnf5 does not know what dnf4 has done.

Uhhh, NO!

continuing the ca-cert issue found with audacious:

error logged by audacious when trying to open a https audio stream:

ERROR ../src/neon/neon.cc:542 [open_request]: <0x7f502c00b2d0> Could not open URL: 1 (0)
ERROR ../src/neon/neon.cc:545 [open_request]: <0x7f502c00b2d0> neon error string: Server certificate verification failed: issuer is not trusted
ERROR ../src/neon/neon.cc:783 [fopen]: <0x7f502c00b2d0> Could not open URL
ERROR ../src/libaudgui/util.cc:337 [audgui_simple_message]: Error playing https://listen-ssvcbfbs.sharp-stream.com/ssvcbfbs22.aac:
Server certificate verification failed: issuer is not trusted
# ca-legacy check
Legacy CAs are set to DEFAULT in file /etc/pki/ca-trust/ca-legacy.conf (affects install/upgrade)
Status of symbolic link /etc/pki/ca-trust/source/ca-bundle.legacy.crt:
/usr/share/pki/ca-trust-legacy/ca-bundle.legacy.default.crt

to fix:

# ca-legacy default
# ca-legacy check
Legacy CAs are set to DEFAULT in file /etc/pki/ca-trust/ca-legacy.conf (affects install/upgrade)
Status of symbolic link /etc/pki/ca-trust/source/ca-bundle.legacy.crt:
/usr/share/pki/ca-trust-legacy/ca-bundle.legacy.default.crt

Any hints or ideas?

only direct upgrades from f43 - even new f43 VMs - are affected.

Could your CA issue be related to this change in F44: Changes/droppingOfCertPemFile - Fedora Project Wiki ?

I saw that change too, and can’t rule it out yet. But then this issue should be reproducible after a F42 → F44 upgrades as well, which is not.
Also can’t reproduce with my test system, upgraded sometime after branching and before beta release.
I guess it’s something current in F43 e.g. ca-certificates upgraded on 2026-03-07

Upgrade  ca-certificates-0:2025.2.80_v9.0.304-1.2.fc43.noarch       Dependency      updates
  Replaced ca-certificates-0:2025.2.80_v9.0.304-1.1.fc43.noarch       Dependency      @System

found this in the dnf system-upgrade log

dnf5[789]: [7035/7035] Removing libgcc-0:15.2.1-7. 100% |   0.0   B/s |  11.0   B |  01m25s
dnf5[789]: >>> Running %posttrans scriptlet: ca-certificates-0:2025.2.80_v9.0.304-6.fc44.no
dnf5[789]: >>> Non-critical error in %posttrans scriptlet: ca-certificates-0:2025.2.80_v9.0
dnf5[789]: Transaction failed: Rpm transaction failed.

F42 → F44

there are no %posttrans scriptlet errors

dnf5[667]:  ca-certificates                                           noarch 2025.2.80_v9.0.304-6.fc44           fedora       2.7 MiB
dnf5[667]:    replacing ca-certificates                               noarch 2025.2.80_v9.0.304-1.1.fc42         updates      2.7 MiB
[...]
audit[667]: AUDIT1138 pid=667 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:rpm_t:s0 msg='op=update sw="ca-certificates-2025.2.80_v9.0.304-6.fc44.noarch" sw_type=rpm key_enforce=0 gpg_res=1 root_dir="/" comm="dnf5" exe=2F7573722F62696E2F646E6635202864656C6574656429 hostname=? addr=? terminal=? res=success'

1 Like