Comment 130 for bug 198453

Luke,

I tried what you suggested and still not working correctly. If I start the flash first, then sound works, but it gets hold of the sound card and no app that uses pulseaudio works. If I start app which uses pulseaudio first, then flash does not work. I am on 64-bit version.

----------------------------------------
> From: <email address hidden>
> To: <email address hidden>
> Date: Mon, 29 Sep 2008 02:28:16 +0000
> Subject: Re: [Bug 198453] Re: Default ALSA device must use PulseAudio, otherwise ALSA applications may fail
>
> Could you please try to do the following:
>
> 1. Kill pulseaudio, either by using "killall pulseaudio" or "pulseaudio -i"
> 2. Remove all .pulse files from your home directory, "rm -r ~/.pulse*"
> 3. Move any .asoundrc files away to a temporary directory, of if you have nothing in them that you want to keep, delete them.
> 4. Restart pulseaudio, either by rebooting, logging out and back in, or running "pulseaudio -D --log-target=syslog"
>
> Then let me know if you can get sound at all from any pulseaudio and
> alsa application.
>
> Thanks.
>
> --
> Default ALSA device must use PulseAudio, otherwise ALSA applications may fail
> https://bugs.launchpad.net/bugs/198453
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in PulseAudio sound server: Confirmed
> Status in “alsa-lib” source package in Ubuntu: Fix Released
> Status in “alsa-plugins” source package in Ubuntu: Fix Released
> Status in “pulseaudio” source package in Ubuntu: Confirmed
> Status in alsa-lib in Ubuntu Hardy: Incomplete
> Status in alsa-plugins in Ubuntu Hardy: Incomplete
> Status in pulseaudio in Ubuntu Hardy: Invalid
>
> Bug description:
> Steps to reproduce:
>
> Run both of these at the same time:
> gst-launch-0.10 audiotestsrc ! pulsesink
> gst-launch-0.10 audiotestsrc ! alsasink
>
> If your default sound device does not support hardware mixing, the second command will fail. ALSA cannot use the device while PulseAudio is using it, and this affects a lot of applications.
>
> Note that if you run the commands the other way around, alsalib will use dmix, and then so will pulseaudio, so there is not as much of a problem this way around (except for the fact that dmix and PA are doing the same job, and you can not control the ALSA-using apps' volumes and routing with PA.)
>
>
> Resolution:
>
> Follow http://pulseaudio.org/wiki/PerfectSetup#ALSAApplications
> i.e. install /etc/asound.conf with:
>
> pcm.pulse {
> type pulse
> }
> ctl.pulse {
> type pulse
> }
> pcm.!default {
> type pulse
> }
> ctl.!default {
> type pulse
> }
>
> Then, install the package "libasound2-plugins", as it contains the required "pcm_pulse" and "ctl_pulse" plugins.
>
> Note, too, that there are some applications that fail with ALSA->Pulse:
>
> SDL* seems to hang with neverball, but that is fixed by installing the PulseAudio backend for SDL (libsdl1.2debian-pulseaudio), which will replace the default ALSA backend.
> WINE has its own issues with regards to device selection, which I don't know a remedy for.
> Skype* also has its own problems, but these aren't fixable by us and should not block us, though should be given some consideraton.
>
> * SDL applications (using libsdl1.2-alsa backend), Skype and possibly other misbehaving applications work properly with later versions of libasound2 & libasound2-plugins from Debian unstable.

_________________________________________________________________
See how Windows Mobile brings your life together—at home, work, or on the go.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/