I'm marking this as wontfix for Eoan, as it's EOL in just a few weeks;
please upgrade to Focal if still affected by this bug.
** Changed in: systemd (Ubuntu Eoan)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: systemd (Debian)
Status: Unknown => 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/1849156
Title:
systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
** No longer affects: ntp (Ubuntu)
** No longer affects: ntp (Ubuntu Eoan)
** No longer affects: ntp (Ubuntu Focal)
** Changed in: systemd (Ubuntu Eoan)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => High
--
You received this bug notificatio
** Bug watch added: Debian Bug tracker #947936
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947936
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947936
Importance: Unknown
Status: Unknown
** Bug watch removed: github.com/systemd/syste
** Tags added: dist-upgrade
** Bug watch removed: Debian Bug tracker #902026
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902026
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
I filed bug 1873031 for the latter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
installed
To manage notifications a
FYI : This also has broken dhcp based ntp info updates
This is hit by the chrony autopkgtests, how did you get this systemd upload to
migrate without fixing that?
$ sudo dhclient dummy0
Failed to try-restart systemd-timesyncd.service: Unit systemd-timesyncd.service
is masked.
--
You received t
FYI - Hi Rbalint, this most likely has exposed/triggered bug 1872183
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
in
This bug was fixed in the package systemd - 245.4-2ubuntu1
---
systemd (245.4-2ubuntu1) focal; urgency=medium
[ Balint Reczey ]
* Merge to Ubuntu from Debian unstable
* Refresh patches
- Dropped changes:
* units: Don't mount tracefs in LXC.
- Remaining changes:
Great @rbalint - the chrony test fixes have landed ~1h ago.
Combined with your upload this should be ok then - thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
systemd-timesyncd.
@paelzer I'm landing this fix in next upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
installed
To manage noti
Debian MP is merged at the end of last Week.
It is in 245.4-2 in debian/unstable since Saturday.
It is not yet in 245.2-1ubuntu3 which is the current focal-proposed.
I was working on bug 1870144 and considering to modify timesyncd there,
but seeing this change coming I'll (on the chrony side) only
For the record the solution is under review at https://salsa.debian.org
/systemd-team/systemd/merge_requests/61
** Changed in: systemd (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
hi, thank you for reply.
comment out line: ConditionFileIsExecutable=!/usr/sbin/VBoxService
works for me.
I had to comment out so line:
ConditionFileIsExecutable=!/usr/sbin/VBoxService
Both are commented out and timesyncd works.
Thank you.
Petr
út 11. 2. 2020 v 7:10 odesílatel Mark - Syminet
Got bit by this as well, recall fixing it a few years ago but must have
clobbered my changes on upgrade bionic -> eoan? Having VirtualBox
installed broke it, fix was to comment out this line in
/lib/systemdd/system/systemd-timesyncd.service.d and restart systemd:
ConditionFileIsExecutable=!/usr/s
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ntp (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
s
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ntp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
system
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
** Tags added: id-5dbb33265d09bf5e5d2ca5df
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
installed
To manage notific
given that dropins are not working well enough, we need something
better.
Possibly we need a generator that disables things harder.
Or update alternatives.
But the problem is that timesyncd should only be a fallback
--
You received this bug notification because you are a member of Ubuntu
B
** Also affects: ntp (Ubuntu Focal)
Importance: Undecided
Assignee: Balint Reczey (rbalint)
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Assignee: Balint Reczey (rbalint)
Status: Confirmed
** Tags removed: rls-ee-incoming
--
You receive
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
** Changed in: ntp (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
installed
To manage notifications about
** Also affects: ntp (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
disable-with-time-daemon.conf was reintroduced after observing the regression
reported at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902026
The final solution is being discussed at
https://github.com/systemd/systemd/issues/7104 .
I'm tempted to just split systemd-timesyncd to a separate
** Also affects: ntp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849156
Title:
systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
I realize that the title makes it sound as though this is intended
behavior. To be clear, in this scenario, neither systemd-
timesyncd.service nor ntp.service start. It's not just systemd-
timesyncd.service that doesn't start, as that would be intended
behavior.
--
You received this bug notific
27 matches
Mail list logo
