I see the same problem, and I am willing to help. 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 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...). Bye Giacomo -- _________________________________________________________________ Giacomo Mulas <[email protected]> _________________________________________________________________ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _________________________________________________________________ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _________________________________________________________________ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Pkg-pulseaudio-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-pulseaudio-devel
