From: Harold Johanssen on
On Fri, 26 Feb 2010 16:07:49 +0000, Harold Johanssen wrote:

> All of a sudden, my applications complain the the sound device is busy.
> This is what I get when trying to run, for example, mplayer:
>
> [AO OSS] audio_setup: Can't open audio device /dev/dsp: Device or
> resource busy
> alsa-lib: pcm_hw.c:1242:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed:
> Device or resource busy
> alsa-lib: pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
> alsa-init: playback open error: Device or resource busy
>
> How can I find out who is monopolizing that device? A look into
> the output from ps awux does not provide much info, in that I have
> nothing but the applications I usually run.

Thanks, everybody. fuser did the trick.
From: The Natural Philosopher on
Robert Heller wrote:
> At Fri, 26 Feb 2010 16:07:49 +0000 (UTC) Harold Johanssen <noemail(a)please.net> wrote:
>
>> All of a sudden, my applications complain the the sound device is
>> busy. This is what I get when trying to run, for example, mplayer:
>>
>> [AO OSS] audio_setup: Can't open audio device /dev/dsp: Device or
>> resource busy
>> alsa-lib: pcm_hw.c:1242:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed:
>> Device or resource busy
>> alsa-lib: pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
>> alsa-init: playback open error: Device or resource busy
>>
>> How can I find out who is monopolizing that device? A look into
>> the output from ps awux does not provide much info, in that I have
>> nothing but the applications I usually run.
>
> Firefox? W/Flash? I've noticed that the flash-plugin will grab
> *exclusive* access to the sound device (even when there is no sound
> associated with the flash object(s)).
>

doesn't with me.
>>
>