Red Hat Bugzilla – Bug 251943
Please set pulse module to "default" if it is installed.
Last modified: 2007-11-30 17:12:13 EST
We would like to activate PulseAudio by default in Rawhide now. For this it
would be very useful if the "pulse" ALSA plugin would be mapped to ALSA's
"default" when the alsa-plugins-pulseaudio package is installed.
Basically I think that this:
should be added to /etc/alsa/pcm/pulseaudio.conf. (that is what works for me,
but my understanding of the ALSA config file format very limited)
alsa-plugins-1.0.14-2.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
this bug was filled against devel but only fixed in f7?
It was fixed both in devel and F7. Comment #1 is an automatic message sent by
Bodhi the staging rpm server which is used only for released Fedora versions.
alsa-plugins-1.0.14-2.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
I don't think this works. I'm not getting any alsa->pulseaudio just by
installing the package in f8. It only works with settings in /etc/asound.conf or
Just adding /etc/alsa/pcm/pulseaudio.conf does not work for setting default. In
fact, there seems to be no reason for adding anything to /etc/alsa/pcm, in any
of the plugin packages. Having the readme files as documentation is sufficient.
I believe that either /etc/alsa/alsa.conf needs to be patched in the alsa-lib
package to load a pulseaudio.conf file, or something needs to set up
/etc/asound.conf. (But will this conflict with a user's setting?) This is the
only way to get alsa pulseaudio working by default in Fedora.
Would be nice of this could be addressed soon, would enable KDE to use
pulseaudio by default.
One problem: we only want pulseaudio to be the default ALSA device when the
daemon is running. I suggest that the first half of pcm/pulseaudio.conf:
should get loaded by default (so we can access the 'pulse' alsa device without
changing the default device). But the second half:
should only be present when the pulseaudio daemon is running. Otherwise alsa
stops working, like so:
[wwoods@brinstar alsa]$ aplay /usr/share/sounds/question.wav
*** PULSEAUDIO: Unable to connect: Connection refused
aplay: main:546: audio open error: Connection refused
Will: If you don't want PA, than don't install it. If you have installed it, we
should set everything up so that most things work out of the box.
If you want PA to release the audio devices, just wait a second, or use
pasuspender. The should be no reason for not running PA -- if it is installed.
I modified alsa-plugins and alsa-lib now so that the pulse plugin actually
becomes the default -- but only if alsa-plugins-pulse is installed.
alsa-lib 1.0.15-0.4.rc3, alsa-plugins 1.0.14-5
This is great, but note that /etc/alsa/pcm/pulseaudio.conf is still never read
by alsa, and you cannot select the "pulse" device. (In fact, all the
/etc/alsa/pcm/... stuff installed by alsa-plugins are completely useless (except
maybe as documentation, but that should be in /usr/share/doc/...)
$ aplay -D pulse
ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM pulse
aplay: main:546: audio open error: No such file or directory
("default" device works, and is pulseaudio.)
Point taken. I did yet another update now which fixes the definition for the
pulse plugin, but the remaining plugins are still not activated properly due to
their ignored config files. I will leave this bug open for now, and hope that it
will be fixed completely after f8.