Re: SV: Problems with sound on thin clients (Was: Unidentified subject!)
Hi,
On 21/03/12 13:41, George wrote:
> From syslog;
> Mar 21 14:25:46 ltsp24 pulseaudio[2662]: ratelimit.c: 331 events suppressed
> Mar 21 14:25:46 ltsp24 pulseaudio[2662]: ratelimit.c: 331 events suppressed
...
Before those messages you should see the original error. Multiple
occurrences of the same error then get suppressed like this.
> When sound stops working I can see this in syslog;
> Mar 21 14:28:56 ltsp24 pulseaudio[2662]: alsa-source.c: snd_pcm_avail:
> Enhet eller resurs upptagen
> Mar 21 14:28:56 ltsp24 pulseaudio[2662]: alsa-source.c: snd_pcm_avail:
> Enhet eller resurs upptagen
> (Enhet eller resurs upptagen=resource busy)
"Device or resource busy" -- I think that means some other program is
directly opening the audio output device, before pulseaudio loads. The
reason for pulseaudio is to avoid this sort of competition for access to
the audio device. dmix is an alternative but could have other drawbacks.
You might be able to find the responsible program by running this at the
shell on the thin client:
$ lsof -nnP | grep pcm
Maybe something like 'timidity' is starting as a daemon and opens the
audio device, before the user logs in and pulseaudio starts.
Regards,
--
Steven Chamberlain
steven@pyro.eu.org
Reply to: