GNOME Software 44 can't launch offline updates on aarch64 (rpi4)
Please describe the issue you’re experiencing: …
On Fedora 38 Workstation (aarch64), GNOME Software is unable to perform offline upgrades, which are failing with:
Feb 20 00:00:33 fedora pk-offline-update[821]: percentage 1%
Feb 20 00:00:33 fedora pk-offline-update[821]: percentage 3%
Feb 20 00:00:34 fedora dnf[819]: trigger file does not exist. exiting quietly.
Feb 20 00:00:34 fedora systemd[1]: dnf-system-upgrade.service: Deactivated successfully.
Feb 20 00:00:34 fedora systemd[1]: Finished dnf-system-upgrade.service - System Upgrade using DNF.
Feb 20 00:00:34 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-system-upgrade comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes>
Feb 20 00:00:34 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-system-upgrade comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 20 00:00:34 fedora systemd[1]: dnf-system-upgrade.service: Consumed 1.393s CPU time.
Feb 20 00:00:34 fedora kernel: audit: type=1130 audit(1676869234.176:65): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-system-upgrade comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a>
Feb 20 00:00:34 fedora kernel: audit: type=1131 audit(1676869234.176:66): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-system-upgrade comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a>
Feb 20 00:00:36 fedora pk-offline-update[821]: percentage 4%
Feb 20 00:00:36 fedora pk-offline-update[821]: percentage 9%
Feb 20 00:00:37 fedora pk-offline-update[821]: percentage 10%
Feb 20 00:00:37 fedora pk-offline-update[821]: percentage 14%
Feb 20 00:00:37 fedora pk-offline-update[821]: sent msg to plymouth 'Installing Updates - 14%'
Feb 20 00:00:38 fedora pk-offline-update[821]: status finished
Feb 20 00:00:38 fedora PackageKit[836]: update-packages transaction /321_bdecdadd from uid 0 finished with failed after 11732ms
Feb 20 00:00:38 fedora pk-offline-update[821]: writing failed results
Feb 20 00:00:38 fedora pk-offline-update[821]: failed to update system: package kernel-6.2.2-300.fc38.aarch64 cannot be verified and repo updates-testing is GPG enabled: /var/cache/PackageKit/38/metadata/updates-testing-38-aarch64/packag>
/var/cache/PackageKit/38/metadata/updates-testing-38-aarch64/packages/kernel-6.2.2-300.fc38.aarch64.rpm: digest: SIGNATURE: NOT OK
Feb 20 00:00:41 fedora systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Signature of the file is okay:
$ rpm -qip /var/cache/PackageKit/38/metadata/updates-testing-38-aarch64/packages/kernel-6.2.2-300.fc38.aarch64.rpm
Name : kernel
Version : 6.2.2
Release : 300.fc38
Architecture: aarch64
Install Date: (not installed)
Group : Unspecified
Size : 0
License : GPLv2 and Redistributable, no modification permitted
Signature : RSA/SHA256, Fri 03 Mar 2023 11:09:53 AM EST, Key ID 809a8d7ceb10b464
Source RPM : kernel-6.2.2-300.fc38.src.rpm
Build Date : Fri 03 Mar 2023 08:24:07 AM EST
Build Host : buildvm-a64-15.iad2.fedoraproject.org
Packager : Fedora Project
Vendor : Fedora Project
URL : https://www.kernel.org/
Bug URL : https://bugz.fedoraproject.org/kernel
Summary : The Linux kernel
Description :
The kernel meta package
What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with?
Fedora 38, Beta Compose Candidate 1.2 (rpm), both gnome-software-44beta-2.fc38 and gnome-software-44rc1.fc38 are affected.
Please attach a log of the issue, by running the following commands, reproducing the issue, and then attaching gnome-software.log
here:
pkill gnome-software
gnome-software --verbose &> gnome-software.log
If the problem is with the user interface, please attach a screenshot or video of it. Please attach the file directly rather than linking to an external hosting service, as external files are likely to be deleted after a while.