Linux Audio Open Error Device Or Resource Busy
Contents |
Help Here Multimedia ALSA sound broken again - "Playback open error: -16,Device or resource busy" Welcome! If this is your first visit, be sure to check out the FAQ. You will have to register before you arecord audio open error: device or resource busy can post in the forums. (Be aware the forums do not accept user names pulseaudio hdmi with a dash "-") Also, logging in lets you avoid the CAPTCHA verification when searching . Select Articles, Forum, or Blog. Posting
Arch Aplay
in the Forums implies acceptance of the Terms and Conditions. Results 1 to 10 of 10 Thread: ALSA sound broken again - "Playback open error: -16,Device or resource busy" Thread Tools Show Printable Version Subscribe
Aplay: Main:722: Audio Open Error: Device Or Resource Busy
to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 07-Aug-2014,19:04 #1 jlturriff View Profile View Forum Posts View Blog Entries View Articles Explorer Penguin Join Date Feb 2009 Location Concordia, MO, USA Posts 139 ALSA sound broken again - "Playback open error: -16,Device or resource busy" Once again, my sound is broken. I can hear but my microphones produce nothing. I'm running 13.1 on x86_64 alsa hdmi ASUS. I don't run PulseAudio because I have never been able to get it to work. aplay -vv /opt/kde3/share/sound/KDE_Beep_Ahem.wav works. speaker-test shows the following: Code: $speaker-test -c2 -D hw:0,0 -l3 -twav speaker-test 1.0.27.2 Playback device is hw:0,0 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Playback open error: -16,Device or resource busy I have run alsa-info.sh and posted the output at Code: http://www.alsa-project.org/db/?f=0fcbef194f4653178cafec084b05cb222f57c2f0 Is there some way to determine what program is locking up the sound card? I can't see anything obvious with top or ps. Leslie Reply With Quote 07-Aug-2014,21:58 #2 gogalthorp View Profile View Forum Posts View Blog Entries View Articles Flux Capacitor Penguin Join Date Nov 2009 Location West by God Virginia Posts 13,027 Re: ALSA sound broken again - "Playback open error: -16,Device or resource busy" lsof /dev/dsp Should list the programs using the sound device in a alsa only system Reply With Quote 07-Aug-2014,22:37 #3 oldcpu View Profile View Forum Posts View Blog Entries Visit Homepage View Articles Global Moderator Join Date Mar 2008 Location Europe Posts 26,820 Re: ALSA sound broken again - "Playback open error: -16,Device or resource busy" Can you run another test ? Try this in a terminal as both a regular user and also with root permissions: Code: apla
on the application hogging the sound device, do: lsof | grep snd This displayed: xmms2d 31732 patrick 7u CHR 116,9 0t0 3885 /dev/snd/controlC0 I
Arecord: Main:722: Audio Open Error: Device Or Resource Busy
could see evidence of the app that was blocking access.I had nothing obvious playback open error: -16,device or resource busy running, so I killed the process. killall xmms2d Then checked again. lsof | grep snd Nothing. Its clear. Done. Labels: Tech aplay: main:722 audio open error no such file or directory Newer Post Older Post Home Blog Archive ► 2015 (186) ► October (4) ► September (2) ► August (22) ► July (25) ► June (25) ► May (47) ► April (47) ► March https://forums.opensuse.org/showthread.php/500157-ALSA-sound-broken-again-quot-Playback-open-error-16-Device-or-resource-busy-quot (13) ► February (1) ► 2014 (109) ► November (11) ► October (17) ► September (11) ► August (27) ► July (39) ► June (3) ► May (1) ► 2013 (37) ► October (4) ► September (2) ► August (10) ► July (3) ► June (2) ► May (1) ► March (3) ► February (1) ► January (11) ► 2012 (47) ► December (14) ► October (7) ► http://stray-notes.blogspot.com/2010/12/aplay-device-or-resource-busy.html August (2) ► July (5) ► May (11) ► January (8) ► 2011 (51) ► November (5) ► September (2) ► August (7) ► July (1) ► June (3) ► May (2) ► April (15) ► February (12) ► January (4) ▼ 2010 (175) ▼ December (25) GnuPG In 10 Minutes Another Sacking For Benitez Aplay: Device Or Resource Busy Chrome Flashplayer 64-Bit Plug-In Add Slime To Emacs Gnu Screen Microsoft Loves Linux Ext4 File System GRUB Multi Disk Multi Boot HowTo Identify Linux Hardware StumpWM MPlayer Crash SSH Login No Password Disable Root Login Using SSH And SCP X Windows Lock Up Emacs Web Jump StumpWM Install Debian Aptitude Too Big Linux Firewall Fujitsu Amilo Laptop MPlayer Audio Track Using Linux Find DVD VOB To AVI ASCII Codes GStreamer unable to detect any sound devices ► November (40) ► October (6) ► September (7) ► August (25) ► July (7) ► June (1) ► May (13) ► April (27) ► March (5) ► February (3) ► January (16) ► 2009 (40) ► December (4) ► November (21) ► October (2) ► September (8) ► February (1) ► January (4) ► 2008 (38) ► December (1) ► November (7) ► October (
Board index The team Delete all board cookies All times are UTC
to test your sound card inputs and outputs by echoing your voice with a short delay. The input is the microphone, and the output is the sound card (or speakers, in this case). I got the test from the Ekiga Wiki. Two days ago it passed with no problem, even after running Ekiga. Now, after attempting to use Ekiga it always fails. Here is the test and the results. $ sudo arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 8000 -f S16_LE -arecord: main:608: audio open error: Device or resource busy aplay: playback:2297: read error If I run it from a fresh boot, I get no error message, but there's no echo. If I run it after starting and terminating Ekiga, I get the error message. The Sound Preferences UI shows that the microphone is working; both Input and Output are at normal volume. Input is "Internal Audio Analog Stereo"; Output is "Analog Output". OK, so what's using the sound devices and what do I do about it? Not really knowing what I'm doing, I tried the following magic that I found on the Internet. $ lsof |grep snd pulseaudi 1649 couture mem REG 8,5 420372 10822043 /usr/lib/libsndfile.so.1.0.20 pulseaudi 1649 couture mem CHR 116,8 4293 /dev/snd/pcmC0D0c pulseaudi 1649 couture 21u CHR 116,10 0t0 4314 /dev/snd/controlC0 pulseaudi 1649 couture 22u CHR 116,10 0t0 4314 /dev/snd/controlC0 pulseaudi 1649 couture 27u CHR 116,8 0t0 4293 /dev/snd/pcmC0D0c pulseaudi 1649 couture 29u CHR 116,10 0t0 4314 /dev/snd/controlC0 gconf-hel 1654 couture mem REG 8,5 420372 10822043 /usr/lib/libsndfile.so.1.0.20 gnome-set 1684 couture mem REG 8,5 420372 10822043 /usr/lib/libsndfile.so.1.0.20 gnome-vol 1777 couture mem REG 8,5 420372 10822043 /usr/lib/libsndfile.so.1.0.20 gnome-vol 1948 couture mem REG 8,5 420372 10822043 /usr/lib/libsndfile.so.1.0.20 ekiga 2000 couture mem REG 8,5 420372 10822043 /usr/lib/libsndfile.so.1.0.20 OK, I don't know where all those other processes came from, but Ekiga is NOT supposed to be running (I had run it and closed it). So, $ killall