Bug 497286 - File transfer box fails to recognize transfer completion. It gets stuck at 99% with no transfer speed when moving massive files into an Android phone
Summary: File transfer box fails to recognize transfer completion. It gets stuck at 99...
Status: RESOLVED DUPLICATE of bug 281270
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 24.08.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2024-12-10 17:42 UTC by Fernando M. Muniz
Modified: 2025-01-09 19:35 UTC (History)
3 users (show)

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


Attachments
It fails to recognize that the transfer is completed. (3.86 MB, video/x-matroska)
2024-12-10 19:32 UTC, Fernando M. Muniz
Details
It seems that the "Response Phase" isn't being checked properly. (37.28 KB, image/jpeg)
2024-12-11 16:52 UTC, Fernando M. Muniz
Details
100% but not 100% even though it's 100% at 100% I'm 100% sure about this one-hundredth percentage. (125.35 KB, image/png)
2025-01-03 20:43 UTC, Fernando M. Muniz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fernando M. Muniz 2024-12-10 17:42:15 UTC
File transfer box is stuck at 99% with no transfer speed when moving massive files to an Android phone.

This must be a bug on Dolphin's end because I always manage to fully extract the supposedly 1% unfinished .tar.gz file after I copy the same file from the phone back into my notebook. Curiously enough, the file transfer always concludes when transferring back.

Which means that Dolphin doesn't recognize the fact that the transferring stopped, even though its transfer speed has stopped and disappeared from the box.
Comment 1 Fernando M. Muniz 2024-12-10 19:32:05 UTC
Created attachment 176498 [details]
It fails to recognize that the transfer is completed.
Comment 2 Fernando M. Muniz 2024-12-11 16:52:43 UTC
Created attachment 176526 [details]
It seems that the "Response Phase" isn't being checked properly.

I'm using Media Transfer Protocol.
Comment 3 Fernando M. Muniz 2024-12-11 17:18:13 UTC
Even if it can't be solved properly on Dolphin's end, it could simply say "File transfering has reached 100% and all bits were transfered but couldn't be automatically verified. Please manually verify the integrity of the transfered file(s)."
Comment 4 TraceyC 2024-12-17 21:38:47 UTC
Details from the attached video:
- The file being transferred is 6.1GB
- File name SSD.tar.gz
- Transferred from local disk to phone over mtp as noted
- The transfer dialog shows 60.1G of 60.1G transferred, transfer speed drops and then disappears when the transfer finishes
- The progress bar still shows 99%

This may be related to bug 281270 which has a related merge request
" When copying files to a removable disk, speed and progress reflect copying to the local cache not to the disk itself"

I tested on git-master with a 3.2GB file (it just has to be large enough to take more than a few moments to copy)
It also used mtp
I wasn't able to replicate. I saw the copy finish notification when the copy finished
This could be a difference in the way the two different phones handle things? I'll leave this open in case someone else can replicate.
Comment 5 Fernando M. Muniz 2024-12-19 10:06:12 UTC
Is it possible that the system is verifying the transferred file's integrity without informing the user?
Comment 6 Fernando M. Muniz 2025-01-03 20:43:32 UTC
Created attachment 177083 [details]
100% but not 100% even though it's 100% at 100% I'm 100% sure about this one-hundredth percentage.

Found an even weirder bug: Reaching 100% doesn't mean it reached 100% even though that doesn't make any mathematical sense.
Comment 7 Fernando M. Muniz 2025-01-06 02:47:08 UTC
In case of multiple heavy files being transferred, the first one never successfully transfers (but actually successfully transfers) and all the other files are never transferred because the first file is never completed even though it actually did.
Comment 8 Akseli Lahtinen 2025-01-09 19:35:13 UTC
This is very likely duplicate of 281270, so I am setting it as  such.

*** This bug has been marked as a duplicate of bug 281270 ***