LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 01-05-2007, 02:52 PM   #1
MQMan
Member
 
Registered: Jan 2004
Location: Los Angeles
Distribution: Slack64 13.37
Posts: 536

Rep: Reputation: 36
KDE gives Sound Server Fatal Error Pop-Up


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.
 
Old 01-05-2007, 04:31 PM   #2
Brian1
Guru
 
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that. Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700

Rep: Reputation: 61
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
 
Old 01-05-2007, 06:04 PM   #3
MQMan
Member
 
Registered: Jan 2004
Location: Los Angeles
Distribution: Slack64 13.37
Posts: 536

Original Poster
Rep: Reputation: 36
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.
 
Old 01-05-2007, 08:20 PM   #4
Brian1
Guru
 
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that. Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700

Rep: Reputation: 61
Do you have the latest KDE installed?

Brian
 
Old 01-05-2007, 08:43 PM   #5
MQMan
Member
 
Registered: Jan 2004
Location: Los Angeles
Distribution: Slack64 13.37
Posts: 536

Original Poster
Rep: Reputation: 36
Everything is off the Slack 11 CDs.

Cheers.
 
Old 01-05-2007, 10:12 PM   #6
Brian1
Guru
 
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that. Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700

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

Brian
 
Old 01-06-2007, 03:13 PM   #7
MQMan
Member
 
Registered: Jan 2004
Location: Los Angeles
Distribution: Slack64 13.37
Posts: 536

Original Poster
Rep: Reputation: 36
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.
 
Old 01-06-2007, 05:05 PM   #8
dive
Senior Member
 
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,211

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


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Sound Server Fatal Error: Error - artsmessage: /tmp/mcop-root is accessible owned... m07hm4n Linux - Software 1 08-14-2006 02:01 PM
sound server fatal error rkfb Slackware 12 02-11-2004 05:48 AM
Sound server fatal error :/ jasonmcneil0 Linux - Newbie 5 10-29-2003 05:22 PM
"Sound server fatal error" (RH 9.0 + KDE) TippyToes Linux - General 1 06-20-2003 02:36 PM
fatal error sound server ramon Linux - Software 0 08-29-2001 03:59 AM


All times are GMT -5. The time now is 05:37 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration