During Fedora 42→43 offline upgrade, system hung at "100% upgrading" for 12+ hours with no visible error or timeout. Required hard reboot to recover. ROOT CAUSE - DEADLOCK: 1. DNF5 offline upgrade holds RPM transaction lock 2. Akmods triggered to build NVIDIA kernel modules 3. Akmods successfully builds modules but cannot install (RPM lock held by DNF5) 4. Akmods holds systemd inhibitor lock while waiting 5. DNF5 tries to reboot but blocked by akmods inhibitor 6. System waits indefinitely with no timeout or user feedback TIMELINE FROM JOURNALCTL: 16:12:29 - Akmods starts, encounters RPM lock: "error: can't create transaction lock on /usr/lib/sysimage/rpm/.rpm.lock (Resource temporarily unavailable)" 16:12:51 - Akmods finishes build successfully (all 5 NVIDIA modules) 16:12:54 - DNF5 tries to reboot: "[org.freedesktop.DBus.Error.AccessDenied] Access denied due to active block inhibitor" 16:12:54 - DNF5 fails: "dnf5-offline-transaction.service: Failed with result 'exit-code'" 16:12:56 - Akmods reports failure but system remains hung 22:36:29+ - System still hung 6+ hours later (no progress) SYSTEM INFO: - akmods-0.6.2-1.fc43.noarch - dnf5-5.2.17.0-2.fc43.x86_64 - systemd-258.1-1.fc43.x86_64 - Hardware: Desktop with NVIDIA RTX 5070 Ti - Kernel: 6.17.5-300.fc43.x86_64 EVIDENCE: Full akmod log available: /var/cache/akmods/nvidia/580.95.05-1-for-6.17.5-300.fc43.x86_64.failed.log (2.8MB) Journal shows DNF5 blocked by inhibitor: Okt 29 16:12:54 bq dnf5[1109]: [org.freedesktop.DBus.Error.AccessDenied] Access denied due to active block inhibitor Okt 29 16:12:54 bq systemd[1]: dnf5-offline-transaction.service: Main process exited, code=exited, status=1/FAILURE EXPECTED BEHAVIOR: System should handle this gracefully with: 1. Timeout mechanism in akmods (e.g., 5 minutes waiting for RPM lock) 2. Release systemd inhibitor lock when akmods fails 3. Visible error message to user (not silent hang) 4. Better coordination between DNF5 offline upgrade and akmods 5. Retry mechanism after reboot ACTUAL BEHAVIOR: - System hangs indefinitely at "100% upgrading" - No error messages visible to user - No timeout or recovery mechanism - Requires manual hard reboot - Zero feedback about what went wrong IMPACT: Affects any Fedora user performing offline upgrade with third-party kernel modules (akmods), particularly common with NVIDIA proprietary drivers via RPMFusion. WORKAROUND: Hard reboot (Ctrl+Alt+Del). After reboot, akmods successfully rebuilt and installed modules. REPRODUCIBILITY: Occurred on desktop with NVIDIA drivers during F42→F43 upgrade. Timing-dependent: happens when akmods service starts before DNF5 releases RPM lock.
FEDORA-EPEL-2025-ca778b21d0 (akmods-0.6.2-3.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-ca778b21d0
FEDORA-EPEL-2025-0449379dd7 (akmods-0.6.2-3.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-0449379dd7
FEDORA-2025-b82f5fa77d (akmods-0.6.2-3.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-b82f5fa77d
FEDORA-2025-b82f5fa77d has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-b82f5fa77d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-b82f5fa77d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-ca778b21d0 has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-ca778b21d0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-9855c8b257 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-9855c8b257` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-9855c8b257 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-0449379dd7 has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-0449379dd7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-bf8ecc9eb6 has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-bf8ecc9eb6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-b82f5fa77d (akmods-0.6.2-3.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
The bug is still happening even on the newest release. This is the error message shown in the journal. GsmManager: Shell confirmed unexpected logout type
FEDORA-2025-9855c8b257 (akmods-0.6.2-3.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-ca778b21d0 (akmods-0.6.2-3.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-0449379dd7 (akmods-0.6.2-3.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.