IMPORTANT CORRECTION -- please ignore my prior message, it contained a major mistake -- this is the corrected version
Okay, that helps explain why the rc.0 one alone did nothing for me -- I'm usually rebooting! ;-/ So the workaround is to do both -- sudo ln -s /etc/init.d/NetworkManager /etc/rc0.d/K40NetworkManager sudo ln -s /etc/init.d/NetworkManager /etc/rc6.d/K40NetworkManager Great job! That's a temporary work-around, and work-arounds are very good -- but when a request to test a patch or a fix comes out, you'll want to return to the previous state and delete those symlinks so you can cleanly test. sudo rm /etc/rc0.d/K40NetworkManager sudo rm /etc/rc6.d/K40NetworkManager For those who'd rather not edit, another work-around is to disconnect network cables, disable networking in nm-applet, or hit the Wi-Fi kill switch either before or during shutdown. If done before choosing shut- down or reboot, the hang is avoided. If done during the hang, then the remaining shutdown hang at the alsa step is shortened from over 2 minutes to under 15 seconds. @Daniel T. Chen -- are you still asking for help or information on this? -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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
