In the case I outlined, the only way I could catch it happening was to shut down and then boot the system off of a Live USB installation, so I could mount the root filesystem and inspect it before NetworkManager was started up again (using the GRUB 'recovery console' and 'drop to a root shell' (without networking) still starts NetworkManager). Interestingly, it only happens one of my two systems, the one that has a 32-bit Kubuntu install on it; the other is a 64-bit install, but I doubt that's relevant, there's probably something else that is installed that allows NetworkManager to complete its shutdown process before the system stops allowing new process creation.
-- Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it didn't use resolvconf for adding its nameserver info - wipes /etc/resolv.conf link https://bugs.launchpad.net/bugs/324233 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
