Ok, it looks like the networkd crash & error message about enslaving a bridge to a bridge was caused by the fact that the network file for one of the bridge ports had a Match on MACAddress and came before the bridge's own network file. Therefore, on restarting networkd matched the port network file to the bridge itself (which had inherited that ports mac address) and hence tried to enslave the bridge to itself with obviously bad consequences.
It did not used to do that on Eoan, but changing the ports Match section to match on the interface's name means I can now restart networkd without it crashing (and without me loosing comms). However, the dispatcher json is still just as mangled as before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884248 Title: networkd-dispatcher gives corrupted information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
