Bugzilla – Bug 118729
artsd slows down system
Last modified: 2005-09-27 02:56:14 UTC
After starting up KDE, I have to kill the artsd process because it is consuming 20% CPU time and making the system very slow and unresponsive (and it's still pretty slow and unresponsive even after this, but not nearly as bad). This system is a brand new 3.6GHz Pentium 4 so a slow CPU isn't the problem I don't think. I've read other bug reports here about arts, and how it doesn't seem to be needed, but then how do you play anything? Amarok needs either the arts or the xine engine selected to play. Selecting the xine engine doesn't work at all; playing a song only takes 1/2 second, and then it moves to the next song, in rapid succession. Only arts works at all, but then playing MP3s takes up a LOT of CPU time between arts and amarok. I didn't think MP3s should consume so many resources; I had no problems playing them in earlier SUSE/KDE versions on much slower hardware in the past.
artsd isn't sttared at all for a new user and we won't fix bugs in there. Make a different bug report if your xine engine is broken, but only after you updated to the final as there were some fixes between RC1 and final
So what's the deal with arts? Is it being phased out or something? And why is it hogging CPU time now? I've been using KDE on SUSE since the KDE 1.x days, and never saw artsd hogging so much CPU time. (Then again, I've never seen SUSE Linux run as slow as it does now; I just upgraded to a 3.6GHz Prescott P4 and SUSE 10.0 RC1 at the same time, and I'm right back to the exact same performance (maybe worse) that I had with a 300 MHz Celeron (the crappy one without any cache). Is this supposed to be progress?