Version: 2:2.2.0-0ubuntu2 (using KDE 4.3.5) OS: Linux Installed from: Ubuntu Packages I'm about to use Amarok (2.2) to synchronize my local music collection with media devices. In my case I'm transfering the data to a iPod Classic (160G) thus I have a great music collection. Anarok is sychronizing the data (local -> Media device) at very slow speed (system copy by using cp or such is fine). Beside of that it is generating a very heavy system load rendering the system unusable. top likes like this: top - 19:43:59 up 6:18, 4 users, load average: 155.96, 157.10, 156.23 Tasks: 307 total, 9 running, 298 sleeping, 0 stopped, 0 zombie Cpu(s): 2.7%us, 3.8%sy, 0.0%ni, 0.0%id, 93.3%wa, 0.1%hi, 0.1%si, 0.0%st Mem: 1802396k total, 1757132k used, 45264k free, 60256k buffers Swap: 1967952k total, 17676k used, 1950276k free, 1323572k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 8994 arno 20 0 467m 102m 40m S 14 5.8 24:24.12 amarok 1405 root 15 -5 0 0 0 S 7 0.0 6:31.30 kcryptd 10828 root 20 0 2584 1304 896 R 2 0.1 0:15.40 top 4 root 15 -5 0 0 0 S 0 0.0 1:00.29 ksoftirqd/0 1436 arno 20 0 295m 40m 9964 S 0 2.3 2:23.56 plasma-desktop 9023 arno 20 0 70468 17m 4064 D 0 1.0 0:01.12 kio_file 9032 arno 20 0 70468 17m 4064 R 0 1.0 0:01.25 kio_file 9064 arno 20 0 70468 17m 4064 D 0 1.0 0:01.09 kio_file 9069 arno 20 0 70468 17m 4064 D 0 1.0 0:01.12 kio_file 9077 arno 20 0 70468 17m 4064 D 0 1.0 0:01.08 kio_file 9088 arno 20 0 70468 17m 4064 D 0 1.0 0:01.22 kio_file 9095 arno 20 0 70468 17m 4064 D 0 1.0 0:01.22 kio_file 9121 arno 20 0 70468 17m 4064 D 0 1.0 0:01.18 kio_file 9127 arno 20 0 70468 17m 4064 D 0 1.0 0:01.17 kio_file 9132 arno 20 0 70468 17m 4064 D 0 1.0 0:01.14 kio_file 9139 arno 20 0 70468 17m 4064 D 0 1.0 0:01.11 kio_file 9142 arno 20 0 70468 17m 4064 D 0 1.0 0:01.12 kio_file I'm guessing the kio_file processes (owned by amarok) are responsible for that. Let me know what informations you need to further investigate this problem. I never had this problem with Amarok 1.4
*** This bug has been marked as a duplicate of bug 218152 ***