I know that there are some plans to replace the plugin by new functionality, so I'm not specifically asking for this to be fixed. I'm putting up this bug so that users who are confused can find it. The cloud image includes the plugin by default, so it's annoying that it returns bogus results. $ sudo dnf reinstall systemd ... You should restart: * Some applications using: sudo systemctl restart systemd-homed sudo systemctl restart systemd-journald sudo systemctl restart systemd-logind sudo systemctl restart systemd-oomd sudo systemctl restart systemd-resolved sudo systemctl restart systemd-udevd sudo systemctl restart systemd-userdbd * These applications manually: (sd-pam) Additionally, there are: - 1 processes requiring reboot For more information run: sudo tracer -iat 1713437258.5820656 Reinstalled: systemd-255.4-1.fc41.x86_64 But if you check with 'systemctl status', systemd-journald and systemd-userdbd were just restarted. (systemd-oomd, systemd-udevd, systemd-resolved are from different subpackages, and systemd-logind has a bug which does not allow it to be restarted). Maybe this is caused by https://fedoraproject.org/wiki/Changes/Restart_services_at_end_of_rpm_transaction? But note that the implementation in the end is different than what we describe in the proposal. We mark units for restart or reload with '/usr/lib/systemd/systemd-update-helper mark-restart-system-units' and systemd has a %transfiletriggerpostun to execute the restarts at the end. This is in Fedora-Cloud-Base-Generic.x86_64-Rawhide-20240415.n.0.qcow2: python3-dnf-plugin-tracer-4.1.2-1.fc40.noarch Reproducible: Always
Thank you very much for the report Zbigniew, I created an upstream issue - https://github.com/FrostyX/tracer/issues/212 But I am not really sure when I will have time to work on this.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-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 '40'. 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 40 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.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.