Red Hat Bugzilla – Bug 413911
no sound, perhaps because pulseaudio, perhaps because it holds /dev/snd/pcmC0D0p in futex
Last modified: 2008-02-29 04:34:03 EST
Description of problem:
Sound "suddenly" stopped working.
This seems related to bug 395581, and the problems is mentioned briefly on
395581#3. But I just saw it on a un-suspended machine, so it is different.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run firefox with flash and rhythmbox and be (im)patient...
Sound not working in flash, rhythmbox and mplayer
[AO_ALSA] alsa-lib: pcm_hw.c:1099:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p
failed: Device or resource busy
[AO_ALSA] alsa-lib: pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave
[AO_ALSA] Playback open error: Device or resource busy
Could not open/initialize audio device -> no sound.
lsof /dev/snd/pcmC0D0p showed that a pulseaudio binary had opened the file.
strace on the process showed that it was waiting in a futex. (I lost the exact
output...) (I don't understand the exact role of pulseaudio yet...)
getfacl /dev/snd/pcmC0D0p showed the right acls.
kill -9 on the pulseaudio process made sound work again.
mplayer should not have attempted to open the device directly. In case you need
to use the ALSA output, ensure uou have the following in /etc/asound.conf or
# pulseaudio plugin configuration
and the package alsa-plugins-pulseaudio installed. For plash, be sure to have
libflashsupport installed. For rhythmbox, pulseaudio gstreamer sink should work:
Please look into System->Preferences->Hardware->Sound to see which output do you
use. If you convigure ALSA as described above, Default and ALSA should, and also
If you are not sure about your setting, please attach the output of
$ gconftool-2 --dump /system/gstreamer/0.10/default
Did the above resolve the situation for you?
I am (was) confused by the fact that it "usually" works, but has been seen to
suddenly stop working. That led me to search for a solution other places than
I did not have alsa-plugins-pulseaudio installed. Installing it gives the
/etc/alsa/pulse-default.conf you mentioned and makes for example mplayer depend
on a running pulseaudio. Does that mean that for F8 all applications that use
ALSA should have a dependency to alsa-plugins-pulseaudio in order to get sound
working the F8 way?
GStreamer Sound playback was set explicitly to my USB sound device. Ok; setting
it to autodetect changes it to work iff pulseaudio is running.
Apparently the problem came because both ALSA and gstreamer was configured to
NOT use pulse and then pulseaudio had been started somehow, and that stopped sound.
On my machine pulseaudio usually isn't started, even though I have seen it
running, so someone must have started it. What and who is responsible for
To wrap my problems up:
- Missing alsa-plugins-pulseaudio
- pulseaudio not started
- Incorrect-but-working sound configuration
My questions and confusion shows that I don't understand the new pulse-centered
Fedora sound architecture good enough. Apparently many things can go wrong and
are hard to trace. Together that makes small problems look like bugs. But I hope
this report can help improving the system so that small problems doesn't look
like bugs ;-)
(In reply to comment #2)
> Does that mean that for F8 all applications that use
> ALSA should have a dependency to alsa-plugins-pulseaudio in order to get sound
> working the F8 way?
No. ALSA can be used without pulseaudio. It just needs the user to be more
careful in respect that he understands why is he bypassing pulseaudio.
> On my machine pulseaudio usually isn't started, even though I have seen it
> running, so someone must have started it. What and who is responsible for
> starting pulseaudio?
Do you use gnome? It is by default the part of your session.
> My questions and confusion shows that I don't understand the new pulse-centered
> Fedora sound architecture good enough. Apparently many things can go wrong and
> are hard to trace. Together that makes small problems look like bugs. But I hope
> this report can help improving the system so that small problems doesn't look
> like bugs ;-)
Well, if you don't understand pulseaudio-centric architecture, I wonder how did
you end up without the ALSA plugin. It is there for gstreamer/pulseaudio unaware
ALSA applications to just work.
I don't know how I ended up without alsa plugin, but perhaps I can find out.
What should have trigged installation of it? I can't find any rpm dependencies
And what should have put pulseaudio in my gnome session?
For the reference, in
and subthread (where Lennart bravely and patiently explains what is going on)
and the referenced bug 425501 I almost got an explanation of how pulseaudio is
started in F8: PulseAudio is started in place of ESD.
AFAICS what is started in session is only pulseaudio-module-x11 "X11 bell and
security modules for the PulseAudio sound server."
The cause of my problems seems to have been that I hadn't run "yum groupinstall
sound-and-video" when upgrading to F8.
It would have been nice if package dependencies alone could have done it, but I
understand that that would have made Fedora very inflexible.
So this is Not-A-Bug, but just a new strong sub-system with a complex