Further digging in journalctl shows: -- Unit systemd-networkd.service has begun starting up. Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-lan: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-net: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-peer: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-plein: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-protea-2: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-protea: netdev ready Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-peer: Gained IPv6LL Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-plein: Gained IPv6LL Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-protea-2: Gained IPv6LL Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-protea: Gained IPv6LL Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: Assertion 'link->state == LINK_STATE_SETTING_ADDRESSES' failed at ../src/network/networkd-link Mar 02 20:37:00 4-ridge-fw1 systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT Mar 02 20:37:00 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 20:37:00 4-ridge-fw1 systemd[1]: Failed to start Network Service.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818340 Title: systemd-networkd core dumps in bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
