Created attachment 47488 [details] Screenshot displaying Dolphin error that it cannot copy the file, which is a syslink Version: unspecified (using KDE 4.4.2) OS: Linux When selecting folders with Dolphin and performing copy operations, Dolphin should simply ignore syslinks and not try to copy them. Reproducible: Didn't try Steps to Reproduce: Try to copy folders with syslinks in them. For instance: $ ls -l .pulse total 168 lrwxrwxrwx 1 dotancohen dotancohen 23 2010-01-04 08:27 6497f78dc3ba2e6c6c0621314b418a3b-runtime -> /tmp/pulse-3uavuaOb9vyJ -rw-r--r-- 1 dotancohen dotancohen 24576 2010-04-17 21:24 d7c37817edb9d1180a2f9a734b4363c9-card-database.tdb -rw-r--r-- 1 dotancohen dotancohen 43 2010-05-08 16:37 d7c37817edb9d1180a2f9a734b4363c9-default-sink -rw-r--r-- 1 dotancohen dotancohen 51 2010-05-08 16:37 d7c37817edb9d1180a2f9a734b4363c9-default-source -rw-r--r-- 1 dotancohen dotancohen 61440 2010-05-05 09:11 d7c37817edb9d1180a2f9a734b4363c9-device-volumes.tdb lrwxrwxrwx 1 dotancohen dotancohen 23 2010-05-28 16:44 d7c37817edb9d1180a2f9a734b4363c9-runtime -> /tmp/pulse-pJA76AcBAanB -rw-r--r-- 1 dotancohen dotancohen 77824 2010-04-29 14:22 d7c37817edb9d1180a2f9a734b4363c9-stream-volumes.tdb See in screenshot that Dolphin could not copy the syslink
Why should symlinks be ignored? It makes no sense. When copied to another filesystem they would be converted to a copy of the file the symlink is pointing to. Otherwise, the symlink is preserved even though the item it points to is changed.
I had suggested that symlinks be ignored as apparently they cannot be copied. The error text says "The file does not exist". If the file that the symlink points to can in fact be copied, then go ahead and copy it! Don't forget about recursion, which could have a folder copying itself until the heat death of the universe.
Dawit, does comment #2 provide the requested information? Please set the bug status.
(In reply to comment #3) > Dawit, does comment #2 provide the requested information? Please set the bug > status. The symlink gets copied so I dunno what this bug report is about. IOW, I cannot reproduce the problem. Perhaps it has been fixed since this bug was reported? No idea, but copying a symlink from one folder to another in the same partition or a different one results in the symlink itself being copied ; so I cannot really reproduce this issue.
Created attachment 84348 [details] Screenshot in English Here is another screenshot, this time in English. The problem is easily reproducible by trying to copy ~/ to an external USB drive, or alternatively for testing purposes copying only ~/.pulse. Note that the machine that I've used to make the current screenshot is not the same machine as the previous screenshot, so the problem is reproducible across machines.
(In reply to comment #5) > Created attachment 84348 [details] > Screenshot in English > > Here is another screenshot, this time in English. > > The problem is easily reproducible by trying to copy ~/ to an external USB > drive, or alternatively for testing purposes copying only ~/.pulse. Note > that the machine that I've used to make the current screenshot is not the > same machine as the previous screenshot, so the problem is reproducible > across machines. I do not have a ~/.pulse directory to try the test, but can you find out what the symlink you are trying to copy is pointing to? Is it a special device, a regular file or a directory? You can use "stat" from the terminal.
Please provide the requested information, if you can still reproduce this issue with recent versions of KIO and Dolphin.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!