running slack 9.1, with kernel 2.6.3 and kde 3.2 after about 5 minutes into kde i get a warning message saying arts server shutting down due to cpu overload ..

not exactly sure how to go about resolving this issue but it seemed to work ok using the 2.4.22 kernel that originally came with slack.. any ideas?

p.s. the sound still works after the arts server shuts down so im wondering if its really any use having it?

With ALSA, there's not really much need for it. ARTS is a high latency sound server that allows you to play more than 1 sound at a time through /dev/dsp. You will notice a delay in your applications that have sound (quake 3, xmms etc), this is arts doing what it does.

Problem is, when applications want direct access to /dev/dsp, they get denied because arts is hogging it.

With alsa, you can configure your .asoundrc file to handle multiple applications playing sound, with no delay. (check alsa website for more info on that) Since alsa is built into the kernel now, it looks like this will be the way to go.

I have my sound server turned off in kde 3.2, but it seems that artsd keeps starting up, and I have to kill it every now and again. I think konqueror may be the culprit.

thanks ill look into that

I had similar problem, helped when I set in KDE control center - sound - sound system - soundcard "Advanced Linux Sound Architecture" instead of "automatic". Also permissions for all sound devices must be set properly when you work not as root.