SUMMARY DESCRIPTIVE When Copying files (F5) between panes (not when moving files) between different drives When a directory- or file-name has a <blank> as the last character or contains characters like ">", ":" then the creation of the directory or file stops with a fail and stops all further coying, and the user has to correct the file/directory name and restart the copy process. this does not happen in the 'move' F5 process STEPS TO REPRODUCE 1. make sure soem directories/files have <blank> -spaces at the end or names contain other offending characters 2. select a dirctory 3. press F5 Copy 4. fail OBSERVED RESULT Copy process stops with a fail EXPECTED RESULT * as this same condition doesn't stop the move of files, i don't think the copy process should fail or the move process is not failing when it should * the bulk copy should stop and allow to skip the copy and continue or correction of the offending filename SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Hi Derek, can you try the same operation with Dolphin? Also, can you try to move the same elements to another partition?
Created attachment 133089 [details] attachment-6155-0.html Using Nautilus : I've created a test1-directory with in it a directory called Auto's 2 and in it directories containign files /Test 1 /Test 1/Auto's /Test 1/Auto's/Ford /file1... /Test 1/Auto's/Landy | defender/file1... notice the blank behind /Ford / and the | before defender, In some of the file names blank spaces have been introduced , and symbols like " . > + | followed or preceded by blanks or both , having a space in the name like "test 1" doesn't create a problem neither in moving neither in copying ==> when creating a directory or file name with a blank at the end or containing symbols like " . > + | there is no problem ==> I've copied the directorys using nautilus to test2 and moved to test3, moving a complete tree structure doesn't cause any problems ,but copying fails on the space at the end and the " | " in the filename and for some of the symbols like " . > + | Using Dolphin I copied test 1 to test4 and moved to test5 having a space in the name like "test 1" doesn create a problem neither in moving neither in copying ==> when creating a directory or file name with a blank at the end or containing symbols like " . > + | there is no problem ==> I've copied the directorys using dolphin to test6 and moved to test7, moving a complete tree structure doesn't seem to cause any problems ,but copying fails on the space at the end of the directory name and the " | " in the filename and for some of the symbols like " . > + | Like in Krusader there might be a wirder problem with Ubuntu checking filenames Derek - On 05/11/2020 21:20, Davide Gianforte wrote: > https://bugs.kde.org/show_bug.cgi?id=428722 > > Davide Gianforte <davide@gengisdave.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > CC| |davide@gengisdave.org > > --- Comment #1 from Davide Gianforte <davide@gengisdave.org> --- > Hi Derek, can you try the same operation with Dolphin? Also, can you try to > move the same elements to another partition? >
Created attachment 133090 [details] attachment-6359-0.html Using Nautilus : I've created a test1-directory with in it a directory called Auto's 2 and in it directories containign files /Test 1 /Test 1/Auto's /Test 1/Auto's/Ford /file1... /Test 1/Auto's/Landy | defender/file1... notice the blank behind /Ford / and the | before defender, In some of the file names blank spaces have been introduced , and symbols like " . > + | followed or preceded by blanks or both , having a space in the name like "test 1" doesn't create a problem neither in moving neither in copying ==> when creating a directory or file name with a blank at the end or containing symbols like " . > + | there is no problem ==> I've copied the directorys using nautilus to test2 and moved to test3, moving a complete tree structure doesn't cause any problems ,but copying fails on the space at the end and the " | " in the filename and for some of the symbols like " . > + | Using Dolphin I copied test 1 to test4 and moved to test5 having a space in the name like "test 1" doesn create a problem neither in moving neither in copying ==> when creating a directory or file name with a blank at the end or containing symbols like " . > + | there is no problem ==> I've copied the directorys using dolphin to test6 and moved to test7, moving a complete tree structure doesn't seem to cause any problems ,but copying fails on the space at the end of the directory name and the " | " in the filename and for some of the symbols like " . > + | Like in Krusader I've repeated these test copying using a single drive/partition and across drives/partitions this leads me to syspect there might be a wider problem with Ubuntu checking filenames Derek - On 05/11/2020 21:20, Davide Gianforte wrote: > https://bugs.kde.org/show_bug.cgi?id=428722 > > Davide Gianforte<davide@gengisdave.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > CC| |davide@gengisdave.org > > --- Comment #1 from Davide Gianforte<davide@gengisdave.org> --- > Hi Derek, can you try the same operation with Dolphin? Also, can you try to > move the same elements to another partition? >
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!
Informations provided