Bug 502270

Summary: sftp copy cannot continue if nearly finished
Product: [Applications] dolphin Reporter: Richard Kellnberger <Richard1.Kellnberger>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: REPORTED ---    
Severity: normal CC: dolphin-bugs-null
Priority: NOR    
Version First Reported In: 24.12.3   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Richard Kellnberger 2025-04-01 10:56:43 UTC 
SUMMARY
If I copy files from the poorly performing Server of my University using its poorly performing wifi, the copy regulary stops.
First the rate goes to 0 B/s, then it reports the inability to read the remote file. I guess, this is a kind of timeout.
If I copy the file again it continues from the *.part file as expected.
If however, this timeout occurs when the file is nearly finished copying (99% done; around 50kB remaining), the copy will not continue. It displays the same error (“File <remote File> cannot be read.” (translated from German)) instantly.


STEPS TO REPRODUCE
1. Copy a file from a sftp server
2. Have it coincidentally time out at 99 %
3. Try to continue the download

OBSERVED RESULT
Refuses to continue

EXPECTED RESULT
Continues

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.14.0-1-MANJARO (64-bit)
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
I though if i could make the 99 % part file reproducible and came up with the following:
Get a file.
Truncate it a little using truncate.
Try to download it.
This reproduces the error, but I do no know if this is a valid approach.