On 11/24/2008 07:05 PM, Robb Topolski wrote: > > - commenting out everything in /usr/share/alsa/pulse.conf: > amixer responds fast > > (The description of this file is, "PulseAudio alsa plugin configuration > file to set the pulseaudio plugin as default output for applications > using alsa when pulseaudio is running." However, pulseaudio is not > running, wasn't running, so why does Aschuring's commenting out of lines > change anything? /usr/share/alsa/pulse.conf calls its config from > /usr/share/alsa/pulse-alsa.conf which appears to set pulse as the > default sound device. Aschuring's tests at the single-user root prompt > create a similar situation to what all these users are reporting where > when the user session is ended, X and pulse are no longer running, and > the alsa configuration is to use pulse.) > > - removing dns in /etc/nsswitch.conf or adding localhost to ipv6 ::1 in > /etc/hosts > amixer responds fast > > (This addresses the networking delay, but not whether alsa should be > looking for pulse at all when the server is not running. Removing dns > from nsswitch.conf is not desirable.) >
If the alsa-lib conffile that libasound2-plugins provides contains the trigger (i.e., redefining pcm.default so that pulse pcm+ctl routing is used preferentially), then everyone should be able to reproduce this symptom in single-user mode by passing the card index explicitly to amixer/alsactl. Can you verify that is the case? -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
