I've got no idea why KT does this but sometimes it will just blast data out at a rate seemingly higher than my internet connection can cope with, and well over what KT's option have set! KT does not show it is uploading loads and loads, but netstat -anp | grep ktorrent will show the outbound queue to be crammed, as do other network tools. I am torrenting something now and to save any risk of legal hot water (IANAL, I know I do not understand the law, I know people do not get in trouble for downloading but uploading, so why take any risks?) I have the global UL limit at 1k/sec and only allow to UL to 2 people (ie lowest possible settings). Once a torrent is started if the global connection limit is set to one and any leeches kicked then no new leeches will appear and no ULs will start. But sometimes, far too regularly, a download and my whole internet connection will die and it is because KT is utterly maxing out my upstream. Given the legal risks with a client uploading when it should not that KT does not appear to honour the user options is a really bad thing. Hence me saying this is a critical bug, but actually it needs to be a level above "data loss". This stands to be "financial threats"! Sometimes when KT is uploading loads when it should not the UL will stop if a leech is kicked or banned. Though the KT UI says a leech is getting data at 1k/sec or less system tools show that is not the case at all. In the below screenshot there were no leeches at all connected at the points of my labels. http://dumpt.com/img/files/f6ru26p0xo2vimxgbmqy.png I used pkill -9 on ktorrent, as root natch, because somehow using the biggest tool against a tool of a program is meant to teach KT a lesson! KT's uploading killed all downloading too, hence me having to restart a music stream. Is there a backdoor or something in KTorrent to make it upload outside of its rules? Because that is what this bug looks like: I say upload to very few and very slowly and sometimes it uploads^W sends lots of data when the options and displayed information make it look it should not. Oh yeah, the IP filter does not work properly either. Ban people from the peer list and they do not appear in the IP filter, and the only way to clear banned IPs is to restart KT. In the last version of KT I used (a major version ago) this functionality did work. Reproducible: Always Steps to Reproduce: I have not seen any way to consistently recreate this, soz. But it happens really rather often.
can you please build ktorrent for KDE Frameworks 5 and run it from Konsole, so that we get some logging output
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported and confirmed, 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 "CONFIRMED" 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!