Red Hat Bugzilla – Bug 307341
pulseaudio causes xmms ALSA to go into 'pause' at end of each song
Last modified: 2007-11-30 17:12:16 EST
Description of problem:
When routing the audio from xmms to pulseaudio by listing 'pulse' as the audio
devide in the ALSA output plugin, the playback stops at the end of each song,
and I need to hit 'pause' to get it moving again. Stopping pulseaudio and
configuring xmms to send to ALSA like it did before pulseaudio showed up works
correctly. Installing the xmms-esd output plugin works, but is a phenomenal
regression. It's bad enough that a program that *used* to be able to route to
the default ALSA device now needs to route to 'pulse' - now I need to install a
frikking *plugin*. Why are we bothering with having ALSA installed at all, if
having a single program that actually *uses* it hoses the whole sound system?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
xmms is just horendously broken and makes assumptions about ALSA that are
I fixed this now in alsa-plugins 1.0.14-4. It's not a hack I am particularly
proud of. But it's a relatively clean fix, given that both xmms and alsa ioplug
are broken and essentially unmaintained.
Couldn't have been *that* clearly invalid an assumption about ALSA, if the bug
went un-noticed/un-fixed for years.
*THAT* bug seems fixed now, but I had the pulseaudio daemon totally evaporate on
me *again* today, just because something else managed to open the device and
pulseaudio didn't want to play nice and work in shared mode. This would
probably work slightly better if the install of pulseaudio had tweaked the right
files so 'pulse' was the default ALSA device, but since that apparently didn't
happen, every time Firefox hits something that uses Flash or mplayer, ker-blammo.
It is a gross misuse of the ALSA API. XMMS checks if playback stopped by waiting
for an XRUN to happen. This is so borked, I am sorry. Just because that works
most of the time it doesn't nmake it better.
Hmm, is this an upgraded system? By default we now activate the pulse plugin for
alsa by default. Also, we install libflashsupprt.so by default, which should
make Flash play nice with PA.
Yes, it started off with a Fedora 7 install back in December and has basically
been following Rawhide ever since, so it's quite possible that 'yum update' has
failed to suck in some RPM that should have been pulled in.
Yep, no libflashsupprt.so here:
% locate libflash
And what needs to be done to activate pulse in alsa 'by default'? I'm certainly
not seeing the appropriate script-fu in 'rpm -q --scripts pulseaudio' (it adds
the user/group, but doesn't fix /etc/alsa/alsa.conf.
"repoquery --whatprovides libflashsupprt.so" comes up empty - this would be
easier to figure out if the appropriate RPM had a Provides: attached to it?
Because of evil multilib libflashsupport.so had to be split off into a seperate
sudo yum install libflashsupport