Bug 402697 - Copying to a FAT filesystem, Files and with Unicode chars cause the whole copy to fail
Summary: Copying to a FAT filesystem, Files and with Unicode chars cause the whole cop...
Status: RESOLVED DUPLICATE of bug 402298
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.44.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-30 04:41 UTC by bluescreenavenger
Modified: 2021-08-09 22:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Archive containing the logs, and the tree, and the Seed.txt file to pass to the kiocopy script (1.00 MB, application/x-xz)
2018-12-30 04:41 UTC, bluescreenavenger
Details
Bash script of which to use to recreate the file tree that failed to copy. Pass the path to the Seed.txt to it. (21.63 KB, application/x-shellscript)
2018-12-30 04:42 UTC, bluescreenavenger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bluescreenavenger 2018-12-30 04:41:18 UTC
Created attachment 117176 [details]
Archive containing the logs, and the tree, and the Seed.txt file to pass to the kiocopy script

SUMMARY
Copying to a FAT filesystem, Files and with Unicode chars cause the whole copy to fail. This might be similar to 402298, although this time I have VALID Unicode chars, as I found a way to correctly count Unicode bytes in Bash for the 255 byte (not char) limit in Linux filesystems.

STEPS TO REPRODUCE
1. Use the Seed file in the attached tar file, pass it as an argument to the kiocopy script.
2. I have the logs and everything attached


OBSERVED RESULT
While I know FAT file systems are going to have problems with Unicode file names and reject them, and I would expect those to fail to copy, my destination folder is empty, there were some top level folders that did NOT have Unicode in their names, that were not copied as well.

EXPECTED RESULT
There are other (top level) folders that did NOT have Unicode chars in their file names that could have copied over. I would have expected 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 18.04
(available in About System)
KDE Plasma Version: 17.12.3
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
The script, and the report will be attached. This will have the tree info, the log output from kioclient5, and the seed file of which can be passed to the script, so that the test can be recreated exactly.
Comment 1 bluescreenavenger 2018-12-30 04:42:10 UTC
Created attachment 117177 [details]
Bash script of which to use to recreate the file tree that failed to copy. Pass the path to the Seed.txt to it.
Comment 2 Ahmad Samir 2021-08-09 22:28:08 UTC
Closing as a duplicate of bug 402298, kio now detects such cases and shows a dialog skip the problematic files or replace any invalid (from destination filesystems' weird POV) characters with an underscore "_".

*** This bug has been marked as a duplicate of bug 402298 ***