My laptop hung after calling NetworkManager on shutdown too this morning. Here the cause was that it tried to deconfigure a network interface which wasn't listed in /etc/network/interfaces (file edited).
What's actually the motivation to call NetworkManager on shutdown? Why deconfigure network interfaces then, if the machine is going to be down anyway? Why telling applications (via DBus?) that the network connection is lost, when those applications are going to be terminated anyway (if they haven't been terminated already)? What problem is the NetworkManager attempting to solve on shutdown? I noticed that some DHCP clients tell the DHCP server, when they disconnect, but why? They received a lease, not a lock, it will expire as it is meant to. So why waste time and energy (and exposing the system to potential bugs) by calling NetworkManager on the way out? -- network-manager fails to stop properly when connected to wireless https://bugs.launchpad.net/bugs/155216 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
