SUMMARY Folder copies pause when encountering FIFOs or Socket files. Copying a folder with these objects, and you get a prompt to [Retry], [Skip], [AutoSkip], or [Cancel]. The cp command does have the ability to copy FIFOs and Sockets (But only if you specify the -a or -r flag) STEPS TO REPRODUCE 1. run kioclient5 copy $XDG_RUNTIME_DIR /tmp/testcopy There are many socket files in $XDG_RUNTIME_DIR typically... No FIFO's usually, but a fifo can be created with mkfifo OBSERVED RESULT You get the prompt that it could not read the files, and have the choice to Retry, Skip, AutoSkip, Cancel. Any other normal file will copy fine. (for another test, I created a large directory with 100,000 subdirectories, 1,399,990 files, 10 FIFOs, and everything copied, except the FIFOs.) EXPECTED RESULT While it might be useless to copy FIFOs and Sockets, it might not be best to have it pause the whole operation. Maybe if possible, copy the FIFO or socket the same way that "cp -a" or "cp -r" would, for minimal interruption SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Testing (available in About System) KDE Plasma Version: 19.03 KDE Frameworks Version: 5.53 Qt Version: 5.12 ADDITIONAL INFORMATION
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
I made sure that I created a FIFO in my XDG_RUNTIME_DIR and the Wayland socket file existed, seems that it doesn't hang now
It skips the FIFOs and the sockets instead of hanginh, which I think is acceptable
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 mark the bug 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!
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!