I have caught KTorrent on more than one occasion UPLOADING for extended periodes of time, at rates far exceeding my set limits. I use the squeduler to set 'Unlimited' between 2 and 11 AM when I've got unlimited bandwidth from my ISP. But otherwise, I set it much lower because of my usage CAP. For the most part, KTorrent respects these limits, but on occasion, I've caught it basically putting out unlimited uploading when it isn't suppose to. When it's happenning, there is nothing in the Ktorrent display to indicate that it is going beyond set limits. But I have seperate applications monitoring network traffic, and it clearly shows up there. No other prog open. Stops & starts with Ktorrent. - Ktorrent V. 4.2.1 in KDE 4.10.2 running on Kubuntu 12.10. But I've noticed it before these versions as well. - I've got Rekonq & Chromium but 99.9% of the time I browse with Firefox. - KTorrent displays show NO indication of additional bandwidth consumption. NONE. - I don't even know what's a 'magnet link'. I've seen the name but never read, setup or used it. Magnet Generator plugin is NOT activated. Next time I catch it, I'm going to test if it affects one specific upload or all at the same time. It could be a bug BUT, I've watch its progress; it's like I got something it wants so it keeps comming back untill its got it all. Starts with a couple of test spikes to test available bandwidth, then starts a slow ramp up. I've watch it reach 600 to 800Kbps on the upstream and stay there until I stopped all torrents. Do some poeple have backdoors into KTorrent to control bandwidth? I can think of NO other explanation for this behavior. Reproducible: Didn't try Steps to Reproduce: 1. Set upload speed low ( 5 kbps ). 2. Put some LARGE popular files available for upload. 3. Use 'System Monitor' to monitor network bandwidth usage. 4. Wait until you see upload in Sys.Mon. reach into the 100kbps range. Actual Results: Starts with a couple of test spikes to test available bandwidth, then starts a slow ramp up. I've watch it reach 600 to 800Kbps on the upstream and stay there until I stopped all torrents. When I restart, after several minutes, it starts again. Expected Results: Stay within the limits. I understand that there may be some overhead to the data transmition. But I am sure that that does not account for this. Feals like a backdoor being used when you got something they want.
Is DHT enabled ? Is there anything open in the search plugin ? Can't seem to reproduce such behavior with a popular torrent. If you see this it would be interesting to take a wireshark trace and post that here or send it to me. Would be interesting to analyze.
Status bar says the DHT is off. At lease, when I check it now, but I've never turned it on myself. "wireshark trace". What is that? I download a few items every week but I've only caught it twice in the pass couple of months; once before KDE 4.10 upgrade, and once after so I don't think the upgrade has anything to do with it. It's rare. That is why I think it is something other than a bug.
Here the same. Ktorrent exceeds the limits. In GUI shows that holding on to the uploads limits, but network monitor shows that differently. DHT off. Ktorrent 4.3.1, KDE SC 4.10.4 and 4.11 beta1.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!