Ktorrent is stuck most of the time, completely unusable, i have to wait at least 20 sec before it comes to life again for a few seconds.
The process is markde as "disk seep" in the system activity window.

Does anyone know what's happening ??

This means KTorrent is waiting for data from disk. What was the last thing you asked KTorrent to do?

bcooksley wrote:This means KTorrent is waiting for data from disk. What was the last thing you asked KTorrent to do?

Nothing in particular, i just have about 10 torrents active.
I don't understand what's going on, it's basically almost unusable.
Maybe it's because it writes on an external usb disk ? But it used to work fine before.

An external USB disk could be slower than an internal disk. If you leave KTorrent for some time, does this disk sleep condition eventually settle down?
Also, what download/upload speeds is it showing?

bcooksley wrote:An external USB disk could be slower than an internal disk. If you leave KTorrent for some time, does this disk sleep condition eventually settle down?

Ktorrent is the only process showing "disk sleep".
The thing is; ktorrent has always been using the external usb drive and it used to work fine. It appeared right after I upgraded from to to 14.04, wich is supsicious.

bcooksley wrote:Also, what download/upload speeds is it showing?

Download/upload speed is fine when the process is no waiting (around 300ko/s) , otherwise it's 0.

Indeed. Could you try to reproduce under a new user, using a few torrents to see if the problem also occurs there?
It may also help to use htop or KSysguard to monitor disk activity to see how intensively KTorrent is accessing the disk.

I changed the setting to use another disk and ktorrent works fine.
The problem seems to come from the usb controller somehow, i had many error in the system logs.

That would explain it. It could be a kernel bug in that case, which would be consistent with the system upgrade causing this issue to appear.

bcooksley wrote:That would explain it. It could be a kernel bug in that case, which would be consistent with the system upgrade causing this issue to appear.

haven't had the time to investigate but it's probably that.

thanks.