This bug was fixed in the package systemd - 245.4-4ubuntu3.13
---------------
systemd (245.4-4ubuntu3.13) focal; urgency=medium
* d/p/dell-clamshell-accel-location-base-with-sku.patch:
Revert incorrect patch (LP: #1942899)
systemd (245.4-4ubuntu3.12) focal; urgency=medium
[ Yao Wei ]
* d/p/dell-clamshell-accel-location-base.patch:
Add ACCEL_LOCATION=base property for Dell clamshell models (LP: #1938259)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5c1be33900edee94da0dc9a4ade8edcd079b4c85
[ Lukas Märdian ]
* Add d/p/lp1934221-resolved-disable-event-sources-before-unreffing-them.patch
- Fix segfault in systemd-resolve (LP: #1934221)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6c401900c70962052f56c7108fdc02fe7f84c9bf
[ Simon Chopin ]
* d/p/lp1914740-network-enable-DHCP-broadcast-flag-if-required-by-in.patch:
- Apply upstream patch to fix Hipersocket DHCP mode (LP: #1914740)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=326ae43b7966d9e7c5f7124027185a79a07fa276
[ Dan Streetman ]
* d/p/lp1934981-correct-suspend-then-sleep-string.patch:
Fix sleep verb used by logind during suspend-then-hibernate
(LP: #1934981)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=997f3a7da3d5db22e3c63626c3f7dc3dff0830b0
* d/p/lp1937238-util-return-the-correct-correct-wd-from-inotify-help.patch:
Fix watch for time sync (LP: #1937238)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=dbabff8a03eb232c19174eff1335cd7cb7d7860c
* d/extra/dhclient-enter-resolved-hook:
Reset start limit counter for systemd-resolved in dhclient hook
(LP: #1939255)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9d3a91a0b70a4b2bcc166f366cd0a880fd494812
* d/p/lp1935051-shared-unit-file-make-sure-the-old-hashmaps-and-sets.patch:
Fix memory leak in path cache (LP: #1935051)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=12d6bdeb35f309158fe8d4242c6dd9be4d067604
*
d/p/lp1934147/0001-cgroup-do-catchup-for-unit-cgroup-inotify-watch-file.patch,
d/p/lp1934147/0002-core-Make-sure-cgroup_oom_queue-is-flushed-on-manage.patch:
Catchup cgroup inotify watch after reexec/reload (LP: #1934147)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=63eabc88b8e0005eb40b15b543538ce35377bdbd
-- Dan Streetman <ddstr...@canonical.com> Tue, 07 Sep 2021 14:37:22
-0400
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1937238
Title:
systemd-time-wait-sync.service stuck in "activating" state after boot,
blocks timers from starting
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
systemd-time-wait-sync service sometimes misses sync completed event
and remains in 'activating' state
[test case]
this isn't consistently reproducable, see original description for
test case
[regression potential]
possible problems with the systemd-time-wait-sync service completing
too early or not completing on time
[scope]
this is needed only for f
this is fixed upstream with commit
f6f4f5fe5395a57f10dd446c7266c53f0673eaac which is in v246, so this is
fixed in h and later already
the service does not exist in b so this does not apply there
[original description]
When I start my server running Ubuntu 20.04 the systemd-time-wait-
sync.service is stuck in "activating" state. I noticed this because
none of the systemd timer units triggered, because all the timers
depend on systemd-time-wait-sync.service. Running "systemctl restart
systemd-time-wait-sync.service" manually works around the problem.
Some logs and command outputs:
raek@mizar:~$ lsb_release -rd
Description: Ubuntu 20.04.2 LTS
Release: 20.04
raek@mizar:~$ systemctl | grep systemd-time-wait-sync.service
systemd-time-wait-sync.service
loaded activating start start Wait Until Kernel Time
Synchronized
raek@mizar:~$ systemctl status systemd-time-wait-sync.service
● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized
Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service;
enabled; vendor preset: enabled)
Active: activating (start) since Thu 2021-07-22 11:06:52 CEST; 27min ago
Docs: man:systemd-time-wait-sync.service(8)
Main PID: 514 (systemd-time-wa)
Tasks: 1 (limit: 9415)
Memory: 972.0K
CGroup: /system.slice/systemd-time-wait-sync.service
└─514 /lib/systemd/systemd-time-wait-sync
Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40
time Thu 2021-07-22 09:06:52.216338 UTC
Warning: journal has been rotated since unit was started, output may be
incomplete.
raek@mizar:~$ journalctl -b -u systemd-time-wait-sync.service
-- Logs begin at Wed 2020-07-08 16:34:13 CEST, end at Thu 2021-07-22 11:36:44
CEST. --
Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40
time Thu 2021-07-22 09:06:52.216338 UTC
raek@mizar:~$ dpkg -S /lib/systemd/system/systemd-time-wait-sync.service
systemd: /lib/systemd/system/systemd-time-wait-sync.service
raek@mizar:~$ apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.11
Candidate: 245.4-4ubuntu3.11
Version table:
*** 245.4-4ubuntu3.11 500
500 http://se.archive.ubuntu.com/ubuntu focal-security/main amd64
Packages
100 /var/lib/dpkg/status
245.4-4ubuntu3.10 500
500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
245.4-4ubuntu3.8 400
400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64
Packages
245.4-4ubuntu3 500
500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937238/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
