A bug was filed upstream against an incorrect sorting of the running torrents when "time left" values are huge. See the attached screenshot. ################################################## Ktorrent does not properly sort torrents in the proper order when the "Time Left" column header is clicked. This sort failure appears to be a problem when ktorrent is dealing with extremely large files, where the time left count includes a large integer number of days. Version-Release number of selected component (if applicable): ktorrent.i686 4.3.1-11.fc20 ################################################## Reproducible: Always Steps to Reproduce: 1. queue-up an extremely large file (tens to hundreds of gigabytes) 2. start downloading 3. observe ktorrent's sort ordering Actual Results: Incorrect sort order Expected Results: Correct sort order It seems that Ktorrent encounters some problems accurately estimating the amount of time remaining for a download when the file sizes are huge (on the order of tens to hundreds of GB). That difficulty notwithstanding, this bug report relates to the improper sorting of the estimates once they have been generated. Specifically, when sorting torrents so that they will be sorted in order of completion (torrents with smallest amount of remaining time to completion ranked at top of list) the ordering is wrong. Some torrents that have thousands of days of estimated remaining time are placed at the top of the list, above those torrents that will be completed in an hour or so. Other torrents that have thousands of days of estimated remaining time are placed at the bottom of the list. See attached screen capture.
Created attachment 89208 [details] Screenshot of incorrect sorting
Based on the screenshots attached to the bug downstream at Fedora bugzilla it seems that only the sorting algorithms "Ktorrent" and "Average Speed" have problems.
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!