Bug 183628

Summary:	Renaming a directory while moving multiple files into it cause a loss of data
Product:	[Frameworks and Libraries] kdelibs	Reporter:	Ludovic Fauvet <etix>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	cfeck
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:

Description Ludovic Fauvet 2009-02-07 23:37:57 UTC

Version:            (using KDE 4.2.0)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Gentoo Packages

Step to reproduce:

1. Start to move (or copy) multiple files into a directory.
2. While the first file is moved, rename this directory.
3. When the next file in the queue is moved an error happen.

Expected results:

- The file should be moved / copied into the new directory name.
or
- In the case of files that are moved, restore the files into their original directory (to avoid a loss of data).

Comment 1 Christoph Feck 2009-06-24 05:18:39 UTC

Can you explain "loss of data"? As far as I see, either a file is moved before the rename, so it is also present in the renamed directory, or the file should be moved after the rename, but this fails, so the file stays in the old source directory.

If I understood this wrong, please clarify. If this can indeed lead to data loss, the severity should be raised.

Comment 2 Ludovic Fauvet 2009-06-28 17:30:29 UTC

Hello Christoph,

I tried to reproduce the bug on Gentoo (kde 4.2.4) and Archlinux (4.3-svn) without success. It seems to me that the bug is finally solved.

Before, when I tried to move files (from one disk to another) they disappeared from their source location first, and if I were renaming the destination, the files remaining in the queue were lost.

Comment 3 Christoph Feck 2009-06-28 18:39:23 UTC

Thanks for testing, after further investigation, this might actually be a duplicate that got fixed with commit r917169.

WebSVN link: http://websvn.kde.org/?view=rev&revision=917169

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