© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I actually encountered this again on an upgrade from Debian buster to bullseye. It gave exactly the same symptoms. The solution this time was to `aa-complain chronyd` followed by `aa-enforce chronyd`. It seems that maybe somehow AppArmor was caching an old profile for `chronyd` somewhere, and this somehow survived multiple reboots on my system.