By chance did you happen to try and change any settings in the alsa config or Sound I/O tab to see if artsd stopped eating resources?
If the arts daemon starts eating up your cpu resources in the vmware image from the official download then you will need to kill the
process.
Use top at the command line to verify that it is running and note the PID. Then use # kill -9 PID to terminate the process.
By chance did you happen to try and change any settings in the alsa config or Sound I/O tab to see if artsd stopped eating resources?
I threw the above post up yesterday because muts asked me to. I did do it in a bit of haste. Using "one line commands" are generally the better approach especially when dealing with the aforementioned type of situation.
Also note that removing the arts daemon from startup will also remove this "problem" from future recurrences.
Through KDE Menu Settings/Sound & Multimedia/Sound Settings--> Under the General Tab I deselected Run with highest... and under the Hardware tab I have selected Advanced Linux Sound Architecture.
This more of a band-aid since artsd still utilizes high cpu, but will still allow one to work with an adequate application response time.
Another option is to select OSS and artsd drops next to nil , but very poor or no sound.
I had this issue as well and I just removed it completely from start up.
update-rc.d -f foobar remove
Kmenu > system > settings > sound & multimedia > sound system
untick "enable sound system"
Antoher solution is to disable the sound in VM-Ware. Like this :
VM -> Settings -> Remove Sound Card
And at the next reboot the process artsd is OK (less than 1% CPU) ... I think it's a bad parametrage between VM-Ware eand the host to pump up the "bt's musik" at startup.