(I'm using KTorrent 1.3DEV)

I've got ONE file that will not complete
I've been stuck at 95.32% for 5 days now. Now I know what you're going to say, just give it some more time and you'll start downloading from a seeder. But for 5 days I've seen 15 seeders in my peer list (they show 100% availability) out of 62 peers. Some of the seeders are showing "NO" to being choked and "NO" to being snubbed. Shouldn't I be downloading from them????

Anyways, I've tried stopping and restarting the download, and selecting manual announce on occasion, all of which has done nothing. Anyone have any suggestions? Is this a bug? I'm going to try upgrading to the latest SVN and see if that helps.

There is definitely a bug, i have the same problem that KTorrent stops downloading after x hours. The only way i can make it download again is restarting KTorrent, so you can try that for the time being.

Yes, I've noticed something similar on some, but not all, torrents. The download just hangs at around 99% and doesn't finish. The only way to get it to complete is to close KT and restart it. While this completes the download, it's not a satisfactory solution to the problem.

Any ideas? I'm a non-programmer myself, so I'm afraid I can't fix it.

@djpearman
I hear you, but remember it stays a develop snapshot where such things can happen from time to time.

stoeptegel wrote:@djpearman
I hear you, but remember it stays a develop snapshot where such things can happen from time to time.

I know I don't mean to have a go at anyone, I'm just letting the devs know that I have a similar problem. Maybe one day, when I have more time, I'll learn to program and contribute myself.

I haven't encountered this yet.

I've got ONE file that will not complete Sad
I've been stuck at 95.32% for 5 days now. Now I know what you're going to say, just give it some more time and you'll start downloading from a seeder. But for 5 days I've seen 15 seeders in my peer list (they show 100% availability) out of 62 peers. Some of the seeders are showing "NO" to being choked and "NO" to being snubbed. Shouldn't I be downloading from them????

Are you seeing download traffic ? In the chunks tab, do you see any strange things ? Do the remaining chunks have downloaders assigned ?

Well, I upgraded to a more recent SVN version. The download started, but then stopped again and now I'm stuck at 98%. It shows only one chunk left to download, and it shows 1 peer assigned to it, progress 26/32, but there is no traffic. Actually, I get a small amount of upload traffic, that quickly dies a few seconds later. But the download traffic is nil. I'm showing a total of 50 peers with about 10 or so seeders now. Maybe the peer assignment to chunks is bad??? Does only 1 peer get assigned to each chunk? I also notice that it's the same dead peer (Bitcomet 0.0.6.0) that this chunk is assigned to. If KTorrent is stalled, shouldn't it try another peer for this last chunk?

*Edit*

I stop and then restarted the download, and a different peer got assiged to the chunk (Unknown client this time). However, it stalled out again after about 30 seconds, and I'm back to nil traffic. It now looks similar to before, tons of peers, about 10 seeders, upload traffic is flickering, download traffic is nil.

ubunt00l wrote:Well, I upgraded to a more recent SVN version. The download started, but then stopped again and now I'm stuck at 98%. It shows only one chunk left to download, and it shows 1 peer assigned to it, progress 26/32, but there is no traffic. Actually, I get a small amount of upload traffic, that quickly dies a few seconds later. But the download traffic is nil. I'm showing a total of 50 peers with about 10 or so seeders now. Maybe the peer assignment to chunks is bad??? Does only 1 peer get assigned to each chunk? I also notice that it's the same dead peer (Bitcomet 0.0.6.0) that this chunk is assigned to. If KTorrent is stalled, shouldn't it try another peer for this last chunk?

Normally it should assign every non choked peer to that last chunk. KT tries to keep 1 peer per chunk, with a few exceptions :
- At the begginning we put a cap of 4 chunks so we get those 4 first fast, so we can start sharing quickly.
- During the download there is a limit to keep memory usage down, if all slots are taken up. We assign the peers who we cannot assign a chunk to an existing chunk download.

There must be an obscure bug with the assignment algorithm.

I noticed the exact same thing, but than when uploading a new torrent as only seeder, see thread
[bug] SVN 505451 uploaded torrent-> peers uncompleted

So maybe this combination illiminate a bug in pipelining.