Bug 198433 - Dolphin gets confused after copying and pasting a renamed folder
Summary: Dolphin gets confused after copying and pasting a renamed folder
Status: RESOLVED DUPLICATE of bug 195385
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: unspecified Unspecified
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-30 18:21 UTC by Hugo Rito
Modified: 2009-07-06 02:58 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Hugo Rito 2009-06-30 18:21:55 UTC 
Version:            (using KDE 4.2.90)

Dolphin messes up if we try to copy, and then paste in the same containing folder, a previously renamed folder.

How to reproduce:
1 - Create folder oldname
2 - F2 to rename oldname to newname
3 - copy newname
4 - paste newname

Dolphin pastes the new folder as oldname and not newname.

This gets even stranger if the renamed folder is not empty. Dolphin will create a folder with the oldname, as described before, and then try to paste copies of the content of newname not inside of oldname but inside newname.
Comment 1 Dario Andres 2009-06-30 19:04:13 UTC 
Here using:

Qt: 4.5.2 (KDE-Qt git commit 46a247a2c9a8c0c4456a02f6a0922d859d88fe76
        Date:   Fri Jun 26 13:45:37 2009 +0200)
KDE: 4.3.60 (KDE 4.3.60 (KDE 4.4 >= 20090624))
kdelibs svn rev. 987857 / kdebase svn rev. 987857
on ArchLinux i686 - Kernel 2.6.30

I can reproduce this behaviour. I wonder if this could be related to some cache issue at KDirLister (or related to bug 192185). I'm going to update my build later to double check
Comment 2 FiNeX 2009-06-30 19:43:00 UTC 
It is still reproducible using r989437.
Comment 3 Frank Reininghaus 2009-06-30 19:58:02 UTC 
Might be related to bug 195385.
Comment 4 FiNeX 2009-06-30 21:21:11 UTC 
@Frank: yes, it could be the same
Comment 5 David Faure 2009-07-06 02:58:24 UTC 

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