Bug 318416

Summary: "Time Downloaded" field may be drastically inaccurate
Product: [Applications] ktorrent Reporter: kdebugs
Component: generalAssignee: Joris Guisson <joris.guisson>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: screenshot: one normal, one with wacky time

Description kdebugs 2013-04-16 02:37:27 UTC
Version: 4.1.3-1ubuntu1
Added a torrent 4/14.  Less than 2 days later, "Time Downloaded" reads over 8 days.
(This does not appear to be fixed bug 271521, as pausing and restarting the torrent doesn't increase the time.)

Reproducible: Sometimes

Steps to Reproduce:
None known
Actual Results:  
When downloading a torrent, the "Time Downloaded" field may be drastically inaccurate.

Expected Results:  
Expected "Time Downloaded" to equal never more than the difference between the "Added" date and the current date.

See screenshot
Comment 1 kdebugs 2013-04-16 02:39:00 UTC
Created attachment 78948 [details]
screenshot: one normal, one with wacky time
Comment 2 kdebugs 2013-04-17 00:45:43 UTC
This bug seems more reproducible than I thought.  I don't know the factor by which it jumps ahead, but the timer does seem to always jump ahead under these conditions:
1) Open a torrent with multiple files, and select only one/some of the file(s).
2) Wait for download finish.  Timer will pause.
3) Select one or more additional files to download.  Download resumes, but timer jumps ahead.  I've seen it jump ahead as little as 1 minute 15 seconds or as much as nearly 2 days.
Comment 3 Andrew Crouthamel 2018-11-10 03:21:26 UTC
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!
Comment 4 Andrew Crouthamel 2018-11-21 04:45:05 UTC
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!
Comment 5 Justin Zobel 2023-01-13 01:36:03 UTC
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!
Comment 6 Bug Janitor Service 2023-01-28 05:08:26 UTC
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!
Comment 7 Bug Janitor Service 2023-02-12 03:50:23 UTC
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!