KDE gives Sound Server Fatal Error Pop-Up

MQMan · 01-05-2007, 01:52 PM

Running a fresh install of Slack 11. Whenever I start KDE, artsd hogs the cpu for a while, and I then get an artsd pop-up with: "Sound server fatal error. CPU overloading, aborting".

Already tried Googling for this and found loads of hits, but nothing that helps. The only suggestions were (1) to force ALSA as the sound system in the Control Panel. This made no difference. Or (2) were problems for a specific, on-board, VIA sound chip, which I don't have.

My "ancient" ISA based card, (Hey, this is a server running re-cycled hardware, and doesn't need all the modern bells & whistles), an ES1688, I believe *is* configured correctly, as I *can* play mp3s from the command line using madplay and mpg321. It's only KDE, or more correctly, aRts that complains.

I've tried this running 2.4.33.3, 2.6.17.13, and huge-2.6.17.13, all giving exactly the same results. Works from command line, fails in KDE.

The only messages I can find that relate to this are:

Code:

unix_connect: can't connect to server (unix:/tmp/ksocket-eddie/The-Tardis.BogoLinux.net-1f76-459c1da8)
unable to connect to sound server
unix_connect: can't connect to server (unix:/tmp/ksocket-eddie/The-Tardis.BogoLinux.net-1f76-459c1da8)
unable to connect to sound server
unix_connect: can't connect to server (unix:/tmp/ksocket-eddie/The-Tardis.BogoLinux.net-1f76-459c1da8)
unable to connect to sound server
unix_connect: can't connect to server (unix:/tmp/ksocket-eddie/The-Tardis.BogoLinux.net-1f76-459c1da8)
unable to connect to sound server

Before the re-build (I was too wimpy to try and upgrade), I was running Slack 10.2 with the 2.6.13 kernel, and everything worked perfectly. There were absolutely no hardware changes made between the 10.2 system, and the 11. Just an install, which included re-formatting the partition.

Thoughts anyone.

Cheers.

Brian1 · 01-05-2007, 03:31 PM

Searching here found many post on the subject. I have seen the issue before but usually configuring Alsa to the latest resolved it. This one mentions setting permissions on the /dev files. http://www.linuxquestions.org/questi...d.php?t=141780 . Search here for more post on the subject.

Brian

MQMan · 01-05-2007, 05:04 PM

I'm not sure it's a problem with ALSA or permissions. I can run command line programs, and get audio. I can fire up xmms from a console window, and get audio. It's just aRts that doesn't want to "play nice".

Cheers.

Brian1 · 01-05-2007, 07:20 PM

Do you have the latest KDE installed?

Brian

MQMan · 01-05-2007, 07:43 PM

Everything is off the Slack 11 CDs.

Cheers.

Brian1 · 01-05-2007, 09:12 PM

Thats about all I know to do is to have the latest stable KDE installed as well as Alsa.

Brian

MQMan · 01-06-2007, 02:13 PM

That seems a drastic step to take, especially as Pat takes some much care over making sure all the packages he puts into each release have all the correct dependencies, and co-exist correctly.

Also, that suggestion smacks more as a "try it and see", as opposed to a "this *is* the fix".

Cheers.

dive · 01-06-2007, 04:05 PM

I've also been having problems with arts. I get an error once and then a message saying that arts will be disabled.