Arch Linux

wolfdogg

Member

From: Portland, OR, USA

Registered: 2011-05-21

Posts: 545

sound over rdesktop error periodic - heres the error message

i am having problems getting sound over my LAN rdesktop to a win machine periodically,

heres the error message

rdesktop -g 1600x1000 -r sound:local *netbiosname* 
Autoselected keyboard map en-us
WARNING: Remote desktop does not support colour depth 24; falling back to 16
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ERROR: snd_pcm_open: Device or resource busy
/dev/dsp: No such file or directory

when i try it with alsa, im getting errors as well

rdesktop -g 1600x1000 -r sound:local:alsa *netbiosname* 
Autoselected keyboard map en-us
WARNING: Remote desktop does not support colour depth 24; falling back to 16
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ERROR: snd_pcm_open: Device or resource busy
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ERROR: snd_pcm_open: Device or resource busy
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ERROR: snd_pcm_open: Device or resource busy
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ERROR: snd_pcm_open: Device or resource busy
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ERROR: snd_pcm_open: Device or resource busy
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ERROR: snd_pcm_open: Device or resource busy
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ERROR: snd_pcm_open: Device or resource busy

before i noticed these error messages happening in the background shell window of rdesktop, i tried to see if the problem was on the output itself, so i tried to play an mp3 to see if my amplifier was correctly pulling the signal from the arch box, and i couldnt play an mp3 either, but this may be related to smb:// errors.  i will tackle that one later.  finally i heard an error beep through my speakers which means archbox is outputting sound correctly, then i saw the error messages which is basically saying that something is tying up my audio device. 

what could be tying it up?

----------
edit

ok i ran lsof

$ lsof /dev/snd/*
COMMAND   PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
knotify4 1527 wolfdogg  mem    CHR  116,3          7434 /dev/snd/pcmC0D0p
knotify4 1527 wolfdogg   19u   CHR  116,3      0t0 7434 /dev/snd/pcmC0D0p

after ending process of knotify the sound is back.  so do i check into a problem with knotify?  when i end the process, it does come back, so i wonder if the next time knotify has to output a sound this will happen again, or some condition unknown will cause it to happen again.

this could be a kernel problem correct?

Last edited by wolfdogg (2011-09-09 20:04:38)

---

Node.js, PHP Software Architect and Engineer (Full-Stack/DevOps)
GitHub  | LinkedIn