This bug was fixed in the package systemd - 229-4ubuntu19
---------------
systemd (229-4ubuntu19) xenial; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)
systemd (229-4ubuntu18) xenial; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
* networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
* Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
* Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
* resolved: fix null pointer dereference crash (LP: #1621396)
* Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
* SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
* Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)
-- Dimitri John Ledkov <x...@ubuntu.com> Mon, 17 Jul 2017 17:00:42
+0100
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9445
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668347
Title:
Unable to set bridge_portpriority with networkd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668347/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
