> I also see the following in dmesg coinciding with the upgrade, I think that's just the result of NM shutting down the network. Do you still have the corresponding NetworkManager logs in /var/log/syslog from that time? It usually says why it shut down the net.
> That's precisely the time that the systemd packages were being configured (udev, libsystemd-daemon0, systemd-shim, systemd-services) Ah nice, that's very helpful to narrow it down indeed. So the current hypothesis is that reinstalling those causes either logind itself to get restarted (which is not intended), or restarting the shim causes some confusion with signals which does that. Can you reproduce this effect by reinstalling udev systemd-shim systemd-services a few times? If so, then the next step would be to enable system D-BUS debugging (https://wiki.ubuntu.com/DebuggingDBus) and let dbus-monitor --system run during the upgrade, to watch the bus traffic and pick up signals/method calls which lead to that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288411 Title: udev restart on upgrade broke my wireless state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1288411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
