This bug was fixed in the package systemd - 249.5-2ubuntu1
---
systemd (249.5-2ubuntu1) jammy; urgency=medium
* Merge to Ubuntu from Debian unstable
- Dropped changes (applied upstream):
+ UBUNTU-units-disable-journald-watchdog.patch
+
Yes.. LXD's system containers and systemd/udev have a special kind of
relationship and we should strive to resolve that situation properly
long-term. I already talked to stgraber about that, but I guess we
should lay out a proper path forward as continuously patching more and
more components of
> Reverting this upstream commit seems to fix the problem:
> https://github.com/systemd/systemd/commit/0299deab53d2a087727a5d04c1500c322c48b63e
lxd and systemd have what I can only describe euphemistically as a
horrible relationship. Instead of carrying another patch on systemd to
get it working
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
--
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/1950794
Title:
DHCPv4 (IAID+DUID) networking broken in
Reverting this upstream commit seems to fix the problem:
https://github.com/systemd/systemd/commit/0299deab53d2a087727a5d04c1500c322c48b63e
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Turns out dropping "debian/patches/units-Don-t-start-systemd-udev-
trigger.service-in-a-conta.patch" (that we want to drop anyway) makes a
difference here, i.e. removing the "ConditionVirtualization=!container"
line from /usr/lib/systemd/service/systemd-udev-trigger.service.
# apt install systemd
6 matches
Mail list logo
