Bug 195385 - Copy file after rename use old file name
Summary: Copy file after rename use old file name
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
: 194522 198433 200098 200521 201081 203828 205439 205812 207331 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-06-05 23:14 UTC by FiNeX
Modified: 2009-09-14 16:43 UTC (History)
20 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description FiNeX 2009-06-05 23:14:38 UTC
1) start dolphin
2) split in two views (or open a new dolphin window)
3) on one view open a remote ftp (the bug is not reproducible on local filesystem due to another bug I've already reported)
4) on the other view open a local directory
5) create a file "TEST" on the local directory
6) rename it to "FOO"
7) copy it and paste to the remote ftp directory

-> It will use the old file name instead the new one.



P.S. 1: I've reproduced the bug even locally, but it is harder due to bug 
#192185

P.S. 2: It is not necessary to use a splitted view or two dolphin windows, but it is more easy to reproduce in this way :-)
Comment 1 Frank Reininghaus 2009-06-06 00:26:31 UTC
Looks like bug 194522.
Comment 2 FiNeX 2009-06-06 09:56:00 UTC
*** Bug 194522 has been marked as a duplicate of this bug. ***
Comment 3 FiNeX 2009-06-06 09:56:05 UTC
You're right. I'll set bug #194522 as dup of this due to a better description.
Comment 4 G Cohen 2009-07-03 10:15:51 UTC
In KDE 4.2.95 (KDE 4.3 RC1) (Kubuntu) this is still the case, but not only for files but also for folders. Actually, reproducing it with a folder is easier as it doesn't involve bug 192185. I have a couple of things to add:

If you refresh the window (F5) after renaming the file/folder, it will copy it with the new name.

This is not restricted to Dolphin only but can be reproduced in Konqueror as well.
Comment 5 David Faure 2009-07-06 02:58:24 UTC
*** Bug 198433 has been marked as a duplicate of this bug. ***
Comment 6 FiNeX 2009-07-13 23:45:51 UTC
*** Bug 200098 has been marked as a duplicate of this bug. ***
Comment 7 FiNeX 2009-07-14 11:23:14 UTC
Could bug 200122 (plasma crash) be related to this?
Comment 8 Yvan Da Silva 2009-07-16 09:55:41 UTC
I've the problem too, I've to refresh manually the dolphin or konqueror content after renaming a file and before copying it.

This bug is related to dolphin and konqueror, as it seems they use the same system to rename.

100% Repeatable.
- Open dolphin or konqueror, rename a file (it will not refresh the name auto so don't do it).
- Copy/paste your "renamed filed" to another folder or tab with other folder.

It will copy a kind of "url" to the destination folder.


Way to solve the problem:

Refresh the current navigation page (dolphin or konqueror) and then copy/paste.
Comment 9 FiNeX 2009-07-18 01:54:41 UTC
*** Bug 200521 has been marked as a duplicate of this bug. ***
Comment 10 FiNeX 2009-07-22 10:31:25 UTC
*** Bug 201081 has been marked as a duplicate of this bug. ***
Comment 11 S. Christian Collins 2009-07-27 16:33:42 UTC
I can confirm this is still an issue in KDE 4.3 RC3.
Comment 12 Frank Schaefer 2009-08-03 15:02:46 UTC
Looks like I'm facing the same bug:

Steps to reproduce:
1.) create a test directory (e.g. ~/test) with a sub-directory called "dir1" which contains at least 1 file (e.g. "file1.txt")
2.) change to the "test"-directory
3.) rename "dir1" to "dir2"
4.) select "dir2"
5.) copy "dir2"
6.) paste into the same director ("test") (with no directory selected in "test" !)

What should happen:
Dolphin should now recognize that the directory already exists and ask for a different name or confirmation of overwriting.

What happens instead:
Dolphin creates "dir1" again and asks for overwriting-confirmation of each file/subdirectory.
That's wrong, because:
1.) noone told Dolphin to create "dir1" again and paste the data there
2.) overwriting confirmation doesn't make sense, because "dir1" has been recreated and is therefore empty
Comment 13 Daniel Mader 2009-08-12 12:06:16 UTC
Still present in 4.3.0. Reproducible on both local and remote filesystems (CIFS and NFS):

After renaming a file and copying it, it gets its old name back in the new location.
Comment 14 FiNeX 2009-08-15 10:54:20 UTC
*** Bug 203828 has been marked as a duplicate of this bug. ***
Comment 15 David Faure 2009-08-17 22:26:43 UTC
SVN commit 1012564 by dfaure:

Fix "Copy file after rename uses old file name". This was due to the "use of the cached item" speedup,
which was finding a kfileitem with an outdated UDS_NAME. Fix will be in KDE-4.3.1.
BUG: 195385


 M  +3 -0      kio/kfileitem.cpp  
 M  +6 -0      tests/kdirmodeltest.cpp  
 M  +15 -0     tests/kfileitemtest.cpp  
 M  +1 -0      tests/kfileitemtest.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1012564
Comment 16 Frank Reininghaus 2009-08-28 11:36:39 UTC
*** Bug 205439 has been marked as a duplicate of this bug. ***
Comment 17 Frank Reininghaus 2009-08-31 19:26:46 UTC
*** Bug 205812 has been marked as a duplicate of this bug. ***
Comment 18 FiNeX 2009-09-14 16:43:01 UTC
*** Bug 207331 has been marked as a duplicate of this bug. ***