Bug 339549

Summary:	unfinished file counted as finished
Product:	[Applications] ktorrent	Reporter:	BryanFRitt <BryanFRitt>
Component:	general	Assignee:	Joris Guisson <joris.guisson>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description BryanFRitt 2014-09-30 23:58:56 UTC

A file selected for download didn't get finished even though ktorrent said that torrent's downloads were complete. KTorrent said it was 50% done for that file, and that the torrent files were finished downloading, and even pased the after torrent data check afterwards. I looked at the file itself and it was obvious that it wasn't done.  (yes, the file was marked for download) 


Reproducible: Didn't try


Actual Results:  
File seleceted didn't complete download, even though KTorrent said it had completed everything.
(The %complete for the file was 50%, and yes it was marked for download) 


Expected Results:  
KTorrent would finish downloading the file, and check that the file was actually done. 


After finding this error, 
exited KTorrent, 
went and finished off the torrent with the same selected files in Vuze, 
exited Vuze, 
went back to KTorrent, 
reran the check, 
now the file was at 100%, and working 
[NTFS on external hard drive]

Comment 1 Andrew Crouthamel 2018-11-12 02:56:02 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-21 04:28:28 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 2023-01-04 07:05:35 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-19 05:14:18 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-02-03 05:03:57 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!