On 11/24/2008 11:27 PM, Robb Topolski wrote:
> @Daniel Chen,
>
> Hi Daniel, you're over my head a little bit. Can you tell me in easier
> terms what you'd like me to try and I'll be happy to try it.
>
> @Any,
>
> What does the PULSE_INTERNAL variable do? Was that a potential fix or
> just a diagnostic test?
>
Robb, my test case asks you to drop to single user (`sudo telinit 1') to
attempt to reproduce the hang. You would have needed to issue `sudo
alsactl -c0 store' once in single user, and if my (corrected) hypothesis
were correct, you would have experienced the hang still (and you should
if $PULSE_INTERNAL is still non-NULL). I would have asked you then to
unset $PULSE_INTERNAL in the alsa-utils initscript.
Luke's test case more quickly identified this culprit -- that
$PULSE_INTERNAL being set leads to any native alsa program to still
probe for pulseaudio, as stated in the modified code for the pulse
pcm+ctl plugin provided in libasound2-plugins.
As stated in my most recent e-mail, the alsa-kernel hang was a red
herring (although still a bug, just not relevant for this particular issue).
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
Status: Triaged => Invalid
--
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
