I found these two bug tickets that could be relevant: https://github.com/home-assistant/operating-system/issues/896
https://github.com/systemd/systemd/issues/8683 I should also add that this seems to happen on the majority of boots for me, but not every boot. So there is some amount of non-determinism involved. I'm not familiar with what service / tool / part of kernel does what in the boot of an Ubuntu 20.04 system, but I might read up on what systemd- time-wait-sync.service waits for to see if I can figure out why that does not happen. Anyway, thanks for helping me debug this issue! ** Bug watch added: github.com/home-assistant/operating-system/issues #896 https://github.com/home-assistant/operating-system/issues/896 ** Bug watch added: github.com/systemd/systemd/issues #8683 https://github.com/systemd/systemd/issues/8683 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937238 Title: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
