[dolphin] [Bug 464225] New: copy/move symbolic link moves link destination instead

S. Christian Collins bugzilla_noreply at kde.org
Fri Jan 13 06:18:11 GMT 2023


https://bugs.kde.org/show_bug.cgi?id=464225

            Bug ID: 464225
           Summary: copy/move symbolic link moves link destination instead
    Classification: Applications
           Product: dolphin
           Version: unspecified
          Platform: Neon
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: s_chriscollins at hotmail.com
                CC: kfm-devel at kde.org
  Target Milestone: ---

If you copy a symbolic link in Dolphin, it pastes the link target instead of
making a copy of the symlink. If you move a symbolic link, it moves the link
target instead while breaking the symbolic link you tried to move. This is a
regression from earlier versions of Dolphin (not sure when was the last good
version) and affects the current development version 23.03.70.

STEPS TO REPRODUCE
1. Create a file (I just made a basic text file called "test.txt")
2. Create two folders: "folder1" and "folder2"
3. Create a symbolic link to "test.txt" in folder1.
4. Move the symbolic link from folder1 to folder2.

OBSERVED RESULT
The "test.txt" file created in step 1 is moved to "folder2" while the symbolic
link created in step 3 remains in "folder1". This link, of course, is now
broken, since it still points to the original location of "test.txt".

EXPECTED RESULT
The symbolic link should have been moved from "folder1" to "folder2" and the
actual "test.txt" file should never have been moved.

If you try copying the symbolic link instead of moving it, you will end up with
a copy of the link target (the actual "test.txt") in folder2 instead of a copy
of the symbolic link.

SOFTWARE/OS VERSIONS
OS: KDE neon Unstable Edition
KDE Plasma Version: 5.26.80
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list