This bug was fixed in the package systemd - 259.5-0ubuntu2
---------------
systemd (259.5-0ubuntu2) resolute; urgency=medium
* Fix handling of VMADDR_CID_ANY in a couple places (LP: #2145027)
- ssh-proxy: return an error if user supplies VMADDR_CID_ANY
- socket-util: filter out VMADDR_CID_ANY in vsock_get_local_cid()
* network-generator: support BOOTIF= and rd.bootif=0 options (LP: #2141588)
* tmpfiles: remove duplicate /run/lock definition (LP: #2146544)
-- Nick Rosbrook <[email protected]> Thu, 02 Apr 2026 08:31:45 -0400
** Changed in: systemd (Ubuntu)
Status: Fix Committed => 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/2146544
Title:
259.5-0ubuntu1 in container triggers non fatal errors on upgrade -
run/lock
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2146544/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
