Bug 320206

Summary:	Dolphin: weird (wrong) behaviour when moving files
Product:	[Unmaintained] kio	Reporter:	tesfabpel
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	adawit, frank78ac
Priority:	NOR
Version:	4.10.3
Target Milestone:	---
Platform:	Other
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description tesfabpel 2013-05-24 09:10:56 UTC

When I tell dolphin to move more than one file into a different directory (on different partition / hard drive) and I click stop on the progress notification, I get some files in the new location and some files in the old one (the files already moved are deleted right away and not after the operation is done)

The correct behaviour should be to copy all the files and AFTER they've been copied delete them from the source location.

Reproducible: Always

Steps to Reproduce:
1. Select more than one file (better if big) or a folder with many files.
2. Move them in a different partition / disk.
3. Stop the action.
Actual Results:  
Some files are in the new location and some files are in the old one (the files already moved are deleted right away and not after the operation is done).
The actual file that was being moved (ex: 700MB) in the new location is not removed (and its size is for ex: 358MB). May cause loss of data if you don't know it and use it!!!

Expected Results:  
Files already copied should stay in BOTH location (or at least deleted from the destination location).

At least it's done in this way in other OS / DE.

PS: Sorry for any error (I'm not english)... -.-

Comment 1 Dawit Alemayehu 2013-07-20 03:38:35 UTC

How can this result in data loss? Canceling a move/copy operation mid-stream should result in a partial file being left in the destination and the original file still being in the source directory. That is correct. Whether or not you knowingly use a partially copied file, which you prevented from being completely copied, is your choice. I just do not see the bug or weird feature here.

I have no idea what other OS do in this case, but that is exactly what happens on the command line as well.

Comment 2 tesfabpel 2013-07-20 07:07:01 UTC

Well, I don't know, but don't you think it's better that when you cancel the operation the file being moved / copied should be deleted in the destination folder?
I think it's better and in some ways it's more "user-friendly" so that they don't get partial files hanging around (IMHO)...

Comment 3 tesfabpel 2013-09-08 09:16:38 UTC

Okay, I've tried it on other DEs and on Windows and MacOS X...
When I hit cancel the last file is deleted, it doesn't stay there partially copied...

Suppose I have to copy 1000+ files from a folder to another (to make a backup for example...), what happens if the copy operation failed for some reason in the middle? Am i really supposed to delete everything and restart again??? Because in other DEs / OSes I can recopy everything ignoring existing files without any problem...

Again, I know that in the command line it works this way, but why then other DEs / OSes remove the partially copied file and KDE doesn't?
Plus, what is the pro to have a partially copied file?

Okay, maybe the command line has to be fixed as well, but until then...

Comment 4 Dawit Alemayehu 2013-09-10 05:52:25 UTC


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