https://bugs.kde.org/show_bug.cgi?id=393145
John I. <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Platform|Gentoo Packages |Fedora RPMs Version|17.12.3 |18.04.3 CC| |[email protected] --- Comment #3 from John I. <[email protected]> --- Same problem, but I encounter it differently. Like the original poster, I am also using details view and have inline rename enabled. 1. Open Dolphin, split the screen (F3). 2. Change the right panel to a directory different from the one in the left panel. 3. Left click on any file in right panel to open it, then close it again. (Without this step, no renaming takes place and there is no problem.) 4. Left click on the same file name that has just been closed in the right panel, keep mouse button pressed, drag it to the left panel and drop it there. Choose 'Move here' from the popup menu. 5. What happens next depends on the timing of the drop, or, when you release the left mouse button. In all cases, after you initiate the drag, the file being moved changes to inline rename mode in the right panel (bounding box becomes visible and name is highlighted). If you drop the file after that has happened, the file is moved normally and no renaming takes place. 6. If you drop the file before the filename in the right panel has gone into rename mode, the next file in the directory below it gets renamed with the moved file's name. 7. By the time the 'Move here' popup menu appears the problem has already happened. The popup is not part of the problem. This is a very specific use case, but I think not uncommon: user opens file, sees what it is and decides to move it somewhere else. In most cases no renaming of other files will happen, but every once in a while unwanted renaming will occur. If this is not noticed at the time, the original of the renamed right panel file will later seem to have vanished (it is there, but under a different name and therefore not recognisable). A logical reaction when finding what appears to be a duplicate file that one knows has previously been moved somewhere else, would be to delete it. This is a problem, since one will actually be deleting a different file. The fact that it happens intermittently (depending on timing of file drop button release) means that it can persist for a long time without being noticed. Fedora 28 KDE Plasma version 5.13.4 KDE Frameworks version 5.48.0 Qt version 5.10.1 Kernel version 4.17.14-202.fc28.x86_64 Dolphin version 18.04.3 I first noticed it about a month ago, following installation of a general KDE upgrade from the fedora repo. I do not know what version I had before. -- You are receiving this mail because: You are watching all bug changes.
