Bug 411473

Summary: KDE Connect corrupts files when transferring from Android to computer
Product: [Applications] kdeconnect Reporter: Nicolas RAOUL <nicolas.raoul>
Component: commonAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nicolas.fella
Priority: NOR    
Version: 1.10   
Target Milestone: ---   
Platform: Android   
OS: Android 9.x   
Latest Commit: Version Fixed In:
Attachments: Picture corrupted by KDE Connect

Description Nicolas RAOUL 2019-08-31 14:34:25 UTC
Created attachment 122436 [details]
Picture corrupted by KDE Connect

SUMMARY
When moving many pictures from Android to Ubuntu, KDE Connect corrupts about 5% of them.

STEPS TO REPRODUCE
1. On Android 9, install Android KDE Connect app from F-Droid (version 1.12.9)
2. On Ubuntu 2019.04, install packages "kdeconnect" and "dolphin"
3. Pair the two
4. In Dolphin, browse your phone to DCIM/Camera, select all pictures (I had about 1500), press CTRL-X
5. Still in Doplphin, go to a folder on your desktop computer, for instance /home/nico/Pictures, and press CTRL-V
6. Wait for the move to finish (no progress bar so check the result folder from time to time)

OBSERVED RESULT
About 5% of the pictures are corrupt. The corrupt files have the expected file size, but somehow when opening them with any image viewer or even GIMP, only the top of the picture shows up properly. Please find attached an example. Corruption seem to happen in streaks, with some long periods with no corruption, then a short period where half of the pictures are corrupt.
Because it is a move, the originals are lost forever.

EXPECTED RESULT
All files should have been moved correctly, with no corruption.
I have been using this computer for months and have never experienced this issue with any other file transfer software (for instance adb).

SOFTWARE/OS VERSIONS
Android KDE Connect 1.12.9
kdeconnect 1.3.4-0ubuntu1
Qt Version: 5.12.2
KDE Frameworks Version: None installed it seems
Comment 1 Nicolas Fella 2019-08-31 22:34:58 UTC

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