Registered Member
|
1) I have a torrent that is supposedly 87% completed, but the file download size shows the same size as the file completed size. The lower pane shows it is missing chunks too. The ETA time looks like it's completely random. The problem is, nothing ever happens. When restarting ktorrent, the file downloaded size changes to different sizes and so does the ETA. I don't know if I am downloading corrupt chunks or what, but the other peers are able to transfer ok. I'm not out of disk space. What's happening? What can I do?
2) When files complete, they start seeding since I have that option on, but I thought it should stop and continue on to the rest of my download queue, right? It never does. 3) I will have a couple files on download and 5 file download limit, then when I click to stop all, they stop. Then I click on start all, and then what looks like 5 random torrents start up, not the last 5 I stopped. 4) My bandwidth can handle at least a couple hundred kb/s when downloading from the internet. However, when I run ktorrrent, I check my network bandwidth and maybe < 50-100 kb/s is used total in up and down bandwidth. When I try to surf the web, the connection is horridly slow. I don't know what's going on. This only happens when ktorrent uses bandwidth, otherwise I can do other things on the net without any problems when that much bandwidth is used by other programs. What's going on...? 5) Feature request: once I fix my queue problem in 2), pleace add a priority download system for torrents and for individuals files in torrents Actually I have what I think is a great idea for a type of downloading queue system as an additional alternative option to the typical max-downloads-at-a-time system, where the queue is handled not by the number of files one can download at a time, but by a bandwidth limit. If higher priority files are up/downloading at slow rates, then lower priority downloads are started, and stopped as necessary when the higher priority file bandwidths increase and decrease, so that all the downloads try to maintain a user-defined bandwidth rate. I'm always disappointed at one time or another with every appication I've used that handles queued downloads (of any type) when I start downloads at night, and in the morning when I've discovered that I didn't get any files because they downloaded slowly, and lower priority files would have transferred faster and all the download "potential" was wasted. It's probably complicated to implement.. but KTorrent could really stand out from the crowd, since this kind of behavior happens especially with torrents. What do you think? |
Registered Member
|
|
Moderator
|
Lots of poisoned chunks ? You should open the log file (~/.kde/share/apps/ktorrent/log) after you shutdown KT. Look for Hash verification errors. This is however a bug, poisoned chunks should not be counted.
Download queue is on the todo list.
Normal behaviour, when you do start all, KT will try to start all torrents. In your case it just hits the limit.
No idea, never had any problems with KT slowing down my net connection (then again I have a 6.6 Mbps connection). Does this also happen with other BitTorrent clients ?
You want to help out, I'm not exactly swimming in spare time at the moment. And there are a couple of big things which have higher priority at the moment. But after that we will see. |
Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]