On Tue, May 05, 2009 at 05:51:50PM +0200, Giacomo Mulas wrote: > I see the same problem, and I am willing to help.
This seems to be quite differnet bug. > Apparently, as far as I can tell, the problem is with the esound module: > when ANY esound client is connected to pulseaudio, pulseaudio keeps the alsa > device open and locked, so that nothing else can access it. Just even a > sound monitor (e.g. the one in gkrellm) is enough for this. > For example, I get: > > gmu...@capitanata:~$ aplay /usr/share/sounds/phone.wav ALSA lib > pcm_dmix.c:1008:(snd_pcm_dmix_open) unable to open slave > aplay: main:590: audio open error: Device or resource busy You should redirect your alsa to use pulseuadio as well, see http://pulseaudio.org/wiki/PerfectSetup#ALSAApplications > The apparent effect, when using a gnome desktop with esound enabled, is that > ONLY applications going through pulseaudio (either directly or via esound > emulation) can use audio (as originally reported). So the problem is that > the pulseaudio server is locking the audio device. I have no clue as to why > this did not happen with the previous pulseaudio version (in sid) and does > with the latest released one. Please let me know if I can help to solve > this, as it is annoying (if I need e.g. to use skype I have to kill > pulseaudio...). For skype see http://pulseaudio.org/wiki/PerfectSetup#ALSAApplications/s Sjoerd -- One learns to itch where one can scratch. -- Ernest Bramah _______________________________________________ Pkg-pulseaudio-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-pulseaudio-devel
