Bug 314105 - move after download moves even if post-download check fails
Summary: move after download moves even if post-download check fails
Status: RESOLVED WORKSFORME
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-30 00:29 UTC by himdel
Modified: 2023-01-19 05:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description himdel 2013-01-30 00:29:53 UTC
When a download reaches 100%, check data when download is finished starts and regardless whether it decided the data was ok or not, move completed downloads is invoked afterwards, leaving my finished downloads folder with files that are potentially still downloading.

Definitely does it in 4.2.1, sorry, can't install newer version.

Reproducible: Always

Steps to Reproduce:
1. enable "check data when download is finished" and "move completed downloads"
2. crash ktorrent mid-download or otherwise corrupt the partially downloaded data (my laptop battery keeps dying, that's why it's a problem for me)
3. restart ktorrent and let it finish downloading (the first time)

Actual Results:  
The check fails, so the download jumps from 100% to, say, 95%, but the file is already moved to the finished downloads folder. (It quietly finishes downloading there, that part is fine, but I can't really expect it has just because it's there, and that's the whole point of having a separate finished folder).

Expected Results:  
The file should stay in partial downloads until it finishes *and* checks ok.

On a vanilla debian wheezy installation, amd64 arch.
Comment 1 Andrew Crouthamel 2018-11-09 01:01:20 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 2 Andrew Crouthamel 2018-11-18 03:23:44 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 3 Justin Zobel 2022-12-20 07:49:40 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 4 Bug Janitor Service 2023-01-04 05:26:53 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 5 Bug Janitor Service 2023-01-19 05:17:10 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!