> you can reproduce it by removing with --no-deps ntrack & restart your > kde session
You mean one could have been running "kded4 --no-deps ntrack" and experience no CPU issues even w/o these updates?! Geez, how would a regular user know that "--no-deps ntrack" was a valid parameter? R-C
