This bug was fixed in the package haveged - 1.9.19-12
Sponsored for Ural Tunaboyu (uralt)
---------------
haveged (1.9.19-12) sid; urgency=medium
[ Daniel Baumann ]
* Simplifying watch file.
[ Dimitri John Ledkov ]
* Adding patch to flush output after printing the startup message, to
avoid confusion of the service "starting up" after receiving sigterm.
* Adding Conflicts=shutdown.target in haveged.service, to actually stop
haveged unit during the shutdown transaction, instead of relying on
systemd-shutdown to kill haveged during the very late catch-all
killall.
[ Dan Streetman ]
* Adding apparmor-profile to allow haveged to bind to unix sockets.
* Adding ConditionVirtualization=!container in haveged.service.
[ Simon Chopin ]
* Verify haveged service is active in autopkgtests, skipped in
containers.
[ Daniel Baumann ]
* Moving apparmor profile to apparmor subdirectory.
* Refreshing flush-startup-output.patch.
-- Daniel Baumann <[email protected]> Fri, 25 Apr 2025 17:58:00 +0200
** Changed in: haveged (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2115388
Title:
Sync haveged from Debian Unstable for questing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haveged/+bug/2115388/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
