You're using the stock Ubuntu LTSP version.
A systemd or network-manager update probably broke it.
I don't think it's a bug in systemd or network-manager; but that update triggered a bug in LTSP that wasn't triggered previously.
I don't know of anyone maintaining the stock Ubuntu LTSP version.
If someone wants to backport a newer LTSP version into stock Ubuntu repositories, he should follow the documentation at https://wiki.ubuntu.com/UbuntuBackports.
Due to lack of time I'm not going to do it, but I'm willing to help anyone that is interested in continuously backporting newer LTSP versions into LTS Ubuntu versions.
You're using the stock Ubuntu LTSP version.
A systemd or network-manager update probably broke it.
I don't think it's a bug in systemd or network-manager; but that update triggered a bug in LTSP that wasn't triggered previously.
I don't know of anyone maintaining the stock Ubuntu LTSP version.
I'm an LTSP developer and I maintain newer versions of LTSP for Ubuntu in this PPA: /launchpad. net/~ts. sch.gr/ +archive/ ubuntu/ ppa
https:/
If you add that PPA in your sources, both in the server and the chroot, and fully update, the problem you saw will probably go away.
I do mention adding the PPA in the recommended LTSP installation instructions: wiki.ltsp. org/wiki/ Installation/ Ubuntu
http://
If someone wants to backport a newer LTSP version into stock Ubuntu repositories, he should follow the documentation at https:/ /wiki.ubuntu. com/UbuntuBackp orts.
Due to lack of time I'm not going to do it, but I'm willing to help anyone that is interested in continuously backporting newer LTSP versions into LTS Ubuntu versions.