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 ]
as systemd was respun due to bug 1942899, and only the one udev (hwdb)
patch was reverted which shouldn't affect this at all, I'm remarking
this as verified still based on testing for the previous version above.
** Tags removed: verification-needed verification-needed-focal
** Tags added:
Hello Rasmus, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.13 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
marking verified per comment 18, thanks!
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
I tested systemd 245.4-4ubuntu3.12 just now. It worked immediately on
three boots!
raek@mizar:~$ apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.12
Candidate: 245.4-4ubuntu3.12
Version table:
*** 245.4-4ubuntu3.12 400
400 http://archive.ubuntu.com/ubuntu
Let me accept this officially into focal-proposed, but I'll request that
@raek - as the person that can fully and reliably reproduces it -
performs the required validation using the exact binary packages from
our official proposed archive.
Thank you!
** Changed in: systemd (Ubuntu Focal)
Dan: I just added the PPA, upgraded the packages and did 3 reboots. In
all cases "systemctl" showed "starting" when I logged in and then
"started" some seconds later. So it seems like the problem is solved!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Rasmus are you able to test with the systemd build from this ppa to see if it
fixes the problem for you:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
> so is there something else not working in focal?
as noted in the [scope] sru template section this is fixed by upstream
commit f6f4f5fe5395a57f10dd446c7266c53f0673eaac which isn't in focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
But the things mentioned in systemd issue were supposedly resolved, and
https://github.com/systemd/systemd/commit/d84af414180a4a8a7dd8772fc9d5302b5f9f28c9
is in focal already.. so is there something else not working in
focal?
--
You received this bug notification because you are a member of
** Description changed:
+ [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
> https://github.com/home-assistant/operating-system/issues/896
yes the upstream commit to fix this does look like what would cause
this, thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
My problem looks similar to the on reported in the Home Assistant bug
tracker.
raek@mizar:~$ systemctl status systemd-time-wait-sync
... *SNIP* ...
└─508
One more boot. This time I checked the timestamp of the
/run/systemd/timesync/synchronized file (and did not run any timedatectl
commands):
raek@mizar:~$ ls -la /run/systemd/timesync
total 0
drwxr-xr-x 2 systemd-timesync systemd-timesync 60 Jul 26 22:51 .
drwxr-xr-x 24 root root
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
Here is the output from the journal from a boot where time-wait-
sync.service "stuck". (I removed some line relating to syncthing and to
a private IRC bot I run.) After boot I logged in, checked "journalctl"
and saw that time-wait-sync.service was "activating" and then ran
"timedatectl status" and
> Hmm. The systemd-timesyncd package is installed and systemd-
timesyncd.service is enabled.
can you attach journalctl output from a full boot reproducing the
problem? I used your exact ntp config and it works fine for me, though
the systemd-time-wait-sync.service does of course stay 'activating'
I opened bug 1938058 for the problem of moving systemd-time-sync-
wait.service into the systemd-timesyncd package, leaving this bug just
for looking at your (possible) problem
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This is my contents of /etc/systemd/timesyncd.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the
Hmm. The systemd-timesyncd package is installed and systemd-
timesyncd.service is enabled.
raek@mizar:~/code/raek-totp-token/firmware$ apt-cache policy systemd-timesyncd
systemd-timesyncd:
Installed: 245.4-4ubuntu3.11
Candidate: 245.4-4ubuntu3.11
Version table:
*** 245.4-4ubuntu3.11 500
This is almost certainly because you don't have the systemd-timesyncd
package installed, or you don't have the systemd-timesyncd service
enabled.
On a very quick glance, it seems the systemd-time-wait-sync service
should have been bundled into the systemd-timesyncd package when it was
split from
This started happen to me in January of February. This is easy for me to
reproduce since it happens at every boot. I would be happy to provide
more information or run more tests if needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
22 matches
Mail list logo
