Hi Dov, I'm glad you posted. It seems I've made the bug Gods angry -- it won't show itself on my system tonight, and I can't figure out why. I hate when that happens.
> I tried killing pulseaudio while logged in to an X session, and it still hung while shutting down. Right. Killing pulseaudio while logged in should show the same problem when the gnome user hits reboot or shutdown. The pulseaudio daemon gets killed then the alsa utility tries to contact it. That is the crux of the issue -- should alsa be trying to contact the pulseaudio server after its killed? Or, should something in the sound configuration revert before pulseaudio gets killed so that the alsa tools don't try to contact the pulseaudio server? I don't understand the architecture well enough to know for certain. The freeze (~ 15 seconds each for 7-10 times that amixer is called to zero and mute the mixer in /etc/init.d/alsa-tools stop) occurs as amixer waits for a DNS query to time out. If the pulseaudio server is alive, the DNS query doesn't happen. If the pulseaudio server is unexpectedly gone, then amixer searches localhost for it. Since it's not found on ipv4 and ipv6 doesn't have localhost in /etc/hosts, the AAAA query goes to the WAN and things pause for 15 seconds while amixer waits for a reply. -- 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
