Opening this bug report in continue to this discussion: https://discussion.fedoraproject.org/t/after-yesterdays-update-fedora-42-is-stuck-during-shutdown-stage-of-restart/150503/4 In short the dnf5daemon-server can stuck the whole shutdown process in case it's checking for upgrades in the DNF repos. In my case it was triggered by dnfdragora-updater that was broken and after recent updated started to work properly. As I wrote in the discussion forum I think the dnfdragora-updater is not guilty in the current restart/shutdown stuck issue. The appropriate part of the logs that accuses dnf5daemon-server is guilty. Take a look on the time gap between Apr 26 01:57:33 and Apr 26 02:02:03. Apr 26 01:57:33 systemd[1]: firewalld.service: Deactivated successfully. Apr 26 01:57:33 systemd[1]: Stopped firewalld.service - firewalld - dynamic firewall daemon. Apr 26 01:57:33 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=firewalld comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Apr 26 01:57:33 systemd[1]: Stopping polkit.service - Authorization Manager... Apr 26 01:57:33 systemd[1]: polkit.service: Deactivated successfully. Apr 26 01:57:33 systemd[1]: Stopped polkit.service - Authorization Manager. Apr 26 01:57:33 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=polkit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Apr 26 01:57:33 audit: BPF prog-id=70 op=UNLOAD Apr 26 01:57:33 audit: BPF prog-id=60 op=UNLOAD Apr 26 02:02:03 dnf5daemon-server[2401]: 2025-04-25T23:02:03+0000 [2401] DEBUG Metadata removal from repository cache in path "/var/cache/dnf5daemon-server/terra-2cbdb71aadff9295" complete. Removed 5 files, 1 directories (total of 731040 bytes). 0 errors Apr 26 02:02:03 dnf5daemon-server[2401]: 2025-04-25T23:02:03+0000 [2401] DEBUG Solv files removal from repository cache in path "/var/cache/dnf5daemon-server/terra-2cbdb71aadff9295" complete. Removed 2 files, 1 directories (total of 803588 bytes). 0 errors Apr 26 02:02:03 dnf5daemon-server[2401]: 2025-04-25T23:02:03+0000 [2401] DEBUG Downloading metadata for repo "terra" Apr 26 02:02:03 dnf5daemon-server[2401]: 2025-04-25T23:02:03+0000 [2401] TRACE countme: no event for repo "terra": window already counted Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] WARNING Error loading repo "terra" (skipping due to "skip_if_unavailable=true"): Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] WARNING std::exception Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] DEBUG Rewriting repo "@System" with added file provides Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] DEBUG Rewriting repo "copr:copr.fedorainfracloud.org:dsommers:openvpn3" with added file provides Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] DEBUG Rewriting repo "updates" with added file provides Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] DEBUG Rewriting repo "fedora" with added file provides Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] DEBUG Rewriting repo "@System" with added file provides Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] DEBUG Rewriting repo "fedora-cisco-openh264" with added file provides Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] DEBUG Rewriting repo "rpmfusion-free" with added file provides Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] DEBUG Rewriting repo "rpmfusion-free-updates" with added file provides Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] DEBUG Rewriting repo "rpmfusion-nonfree-updates" with added file provides Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] DEBUG Rewriting repo "rpmfusion-nonfree" with added file provides Apr 26 02:02:05 dnf5daemon-server[2401]: 2025-04-25T23:02:05+0000 [2401] DEBUG Rewriting repo "code" with added file provides Apr 26 02:02:05 systemd[1]: dnf5daemon-server.service: Deactivated successfully. Apr 26 02:02:05 systemd[1]: Stopped dnf5daemon-server.service - DNF daemon. Apr 26 02:02:05 systemd[1]: dnf5daemon-server.service: Consumed 1.041s CPU time, 323.4M memory peak. Apr 26 02:02:05 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5daemon-server comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Apr 26 02:02:05 systemd[1]: Stopped target basic.target - Basic System. $ dnf info dnf5daemon-server Updating and loading repositories: Repositories loaded. Installed packages Name : dnf5daemon-server Epoch : 0 Version : 5.2.13.0 Release : 1.fc42 Architecture : x86_64 Installed size : 643.9 KiB Source : dnf5-5.2.13.0-1.fc42.src.rpm From repository : updates Summary : Package management service with a DBus interface URL : https://github.com/rpm-software-management/dnf5 License : GPL-2.0-or-later Description : Package management service with a DBus interface. Vendor : Fedora Project Reproducible: Always Steps to Reproduce: 1. Just try to restart Fedora when dnfdragora-updater is running 2. In case everything is ok try yet another time because this issue is reproducable only in 80 - 90 % of times. 3. Actual Results: System is stuck for a very very long time or forever during the shutdown stage of the graceful restart/reboot process. Additional Information: As a workaround I disabled running dnfdragora-updater in the Startup Applications.
Hallo, It is still a very time consuming bug. (it takes 5 mins to stop the process ) F44beta, my workaround is: [Unit] Description=DNF daemon [Service] Type=dbus BusName=org.rpm.dnf.v0 User=root ExecStart=/usr/sbin/dnf5daemon-server TimeoutStopSec=15sec. Change TimeoutStopSec from 5 min to 15 sec.
I can confirm that I also see it from time to time on my F44. I supposed it could be related to bug 2458182 , but if you don't have any such repos, then it's a general problem.
I am experiencing this too in my Fedora 44 Workstation.
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '42'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
I am also seeing this on Fedora 44 Workstation. I do not see the GNOME Software issues linked here and reported under https://bugzilla.redhat.com/show_bug.cgi?id=2458182 so I would suggest that while potentially linked they are not the same. I also do not believe that this should be closed under F42 EoL as clearly this is an unresolved dnf5daemon-server issue and is not explicitly linked to a specific Fedora release. For context this is what I am experiencing, along with my system config: === Environment === Fedora release 44 (Forty Four) 7.0.4-200.fc44.x86_64 dnf5daemon-server-5.4.2.0-1.fc44.x86_64 dnf5-5.4.2.0-1.fc44.x86_64 === Shutdown hang evidence === --- Last activity before hang --- May 12 12:42:02 gw-fw13-02 systemd[1]: sys-devices-pci0000:00-0000:00:0d.2-domain0.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for bolt.service/start is destructive (poweroff.target has 'start' job queued, but 'stop' is included in transaction). May 12 12:42:02 gw-fw13-02 systemd[1]: Requested transaction contradicts existing jobs: Transaction for bolt.service/start is destructive (poweroff.target has 'start' job queued, but 'stop' is included in transaction). May 12 12:42:02 gw-fw13-02 systemd[1]: sys-devices-pci0000:00-0000:00:0d.2-domain0.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for bolt.service/start is destructive (poweroff.target has 'start' job queued, but 'stop' is included in transaction). --- dnf5daemon stop sequence --- May 11 15:30:47 gw-fw13-02 systemd[1]: Starting dnf5daemon-server.service - DNF daemon... May 11 15:30:48 gw-fw13-02 systemd[1]: Started dnf5daemon-server.service - DNF daemon. May 12 12:41:57 gw-fw13-02 systemd[1]: Stopping dnf5daemon-server.service - DNF daemon... May 12 12:46:57 gw-fw13-02 systemd[1]: dnf5daemon-server.service: State 'stop-sigterm' timed out. Aborting. May 12 12:46:57 gw-fw13-02 systemd[1]: dnf5daemon-server.service: Killing process 12841 (dnf5daemon-serv) with signal SIGABRT. May 12 12:46:57 gw-fw13-02 systemd-coredump[99414]: Process 12841 (dnf5daemon-serv) of user 0 terminated abnormally with signal 6/ABRT, processing... May 12 12:46:57 gw-fw13-02 systemd[1]: dnf5daemon-server.service: Main process exited, code=dumped, status=6/ABRT May 12 12:46:57 gw-fw13-02 systemd[1]: dnf5daemon-server.service: Failed with result 'timeout'. May 12 12:46:57 gw-fw13-02 systemd[1]: Stopped dnf5daemon-server.service - DNF daemon. May 12 12:46:57 gw-fw13-02 systemd[1]: dnf5daemon-server.service: Consumed 13.934s CPU time over 10h 14min 39.350s wall clock time, 614.9M memory peak. --- Resource usage at termination --- May 12 12:46:57 gw-fw13-02 systemd[1]: dnf5daemon-server.service: Consumed 13.934s CPU time over 10h 14min 39.350s wall clock time, 614.9M memory peak.
(In reply to Graham Watts from comment #5) > I do not see the GNOME Software issues linked here and reported under > https://bugzilla.redhat.com/show_bug.cgi?id=2458182 so I would suggest that > while potentially linked they are not the same. Yes, they are related, but not the same. Especially comment 0 talks about KDE and not GNOME. > I also do not believe that this should be closed under F42 EoL as clearly > this is an unresolved dnf5daemon-server issue and is not explicitly linked > to a specific Fedora release. The Version got already bumped to 44.
(In reply to Graham Watts from comment #5) > I am also seeing this on Fedora 44 Workstation. > > dnf5daemon-server-5.4.2.0-1.fc44.x86_64 Try upgrading to 5.4.2.1 to exclude a different bug (5-minute timeout when processing repositories with repo_gpgcheck=1 option).