Amarok hums along just fine with Ruby dead and gone.. no functionality is lost in Amarok - that I can see.
Is Amarok running a script you don't use which is triggering ruby to start in the first place?
Checked that just now... no scripts are (currently) started according to the script manager. It could be a script which is spawning Ruby.... don't know what though... Oh, and Amarok is not set up to monitor a directory for new music... so it's not polling the hard drive. A little experimenting... it's the Fetch Lyrics sript that is spawning Ruby - starting the script starts Ruby, and stopping the script stops Ruby. Ok, so now I know what is likely starting Ruby... I wonder what is going wrong that makes Ruby spike the CPU like that. Weird... C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org