Indeed the "[ ] Enable network" menu entry isn't rfkill, sorry. That's "[ ] Enable wireless network". I think "Enable network" just pokes org.freedesktop.NetworkManager.Enable(False/True), which tells NM to shut down/restart all interfaces. Aside from this manual operation the main automatic thing to indirectly call this that I know of is logind: it sends a PrepareForSleep(True) signal right before suspend, and a PrepareForSleep(False) signal after resuming; NM listens to that signal and then does the equivalent of Enable(False/True), to restart the network after resuming.
Now, suspend certainly wasn't involved here either, but during your upgrade systemd-services/libpam-systemd were upgraded as well. Their maint scripts don't do anything to manually restart them, but perhaps logind wasn't running before the upgrade and starting it had such a funky effect? Do you have any /var/crash/* which could be related? And then, it might be possible that other packages restarted something which triggered some network change (libvirt?). But I've never seen this effect myself, so it's hard to guess. Can you trigger this again by apt- get install --reinstall'ing everything that got upgraded in that batch? -- 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
