see #295136. The problem is actually in the amixer executable, which gets invoked about 15 times during shutdown. The problem is reproducable (for me) by running amixer in single-user mode. strace log can be found in the mentioned report.
For reference, see the following note in the news section on http://0pointer.de/lennart/projects/nss-mdns/: "Please note that due to security reasons from this release on the minimal mDNS stack included in nss-mdns (dubbed "legacy") is no longer built by default. Thus, nss-mdns will not work unless Avahi is running! That makes Avahi essentially a hard dependency of nss-mdns." And see the following lines in the strace log: 0.000069 open("/lib/libnss_mdns4_minimal.so.2", O_RDONLY) = 5 0.000069 connect(5, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.1.1")}, 28) = 0 4.013297 ioctl(5, FIONREAD, [37]) = 0 That still does not answer the question why the ** amixer needs to do dns resolution in the first place... -- 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
