https://bugs.kde.org/show_bug.cgi?id=414478
Bug ID: 414478
Summary: User Should definitely be warned every time an Invalid
filename is used!
Product: dolphin
Version: 19.08.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: jc_josue3...@hotmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
Always!But specially when copying or creating files in a NTFS filesystem shared
with Windows.
My experience is that it can indeed lead to data loss!
But why? Even if the NTFS file system doesn't usually accept those files being
created, Linux usually allows them to copied to such partition or even worse,
to be created, and nothing seems to happen, nothing seems to go wrong. But
that's not the reality.
The case is that I had the problem with those files. If that NTFS partition
ever needs to be checked with chkdsk any and all files that had invalid
filenames will go into the brink of being wiped. Granted that if all of them do
appear in the recovered found.000 folders, they will appear with a numerical
name and a .chk extension. If you happen to have created too many invalid files
like I did (and I tried to avoid it, mind you) you will have to go over quite a
high number of files (and folders!) that have lost their meaning because you
don't know where they belong and they lack a proper filename! And it is not
uncommon for Windows to prompt you to check external drives!
Now the trick here is what happens when you have a huge disk with lots of files
and folders and some files start giving "unreadable" or "read access" errors!
You must run chkdsk! The disk is just fine, but those invalid files seem to be
causing the problem when there are too many of them, as they are shown as
offenders in the chkdsk report!
The following reserved characters:
< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)
Linux DOESNT forbid you from creating invalid filenames even on a NTFS
filesystem that is shared with Windows!
If you want to make a map named Dark Archons : the gathering the : character
will make that file go wrong on Windows, If you copy the file to an external
HDD with NTFS it will NOT give any warnings either!!!
https://stackoverflow.com/questions/1976007/what-characters-are-forbidden-in-windows-and-linux-directory-names
Dolphin should definitely give a WARNING message when dealing with files that
have this kind of characters!
I could even create files with * | / ? or \ or even the line break (intro)
character!
--------------------------------------------------------------
SUMMARY
User Should definitely be warned every time an Invalid filename is used when it
comes to copying or creating a file!
Always!
BTW I really think we must put pressure so Microsoft Open Sources NTFS just as
they did with FAT32.
STEPS TO REPRODUCE
1. right click and select create new file or folder
2. type any sort of garbage name, even with * / \ or even |
3. cut or copy the file anywhere! (specially NTFS partitions)
OBSERVED RESULT
No warning, no notice, you could loose those files without ever noticing!
EXPECTED RESULT
A propper warning should be given, even if mass copying.
This should be treated in the same way as when you have duplicated filenames,
Dolphin should allow renaming the offending file or folder!
It would be even better if it suggests a filename removing the offending
characters or even better if (when mass copying) there was an option to review
all the offending files (with a location list) later.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro KDE Juhraya 18.1.3
(available in About System)
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
ADDITIONAL INFORMATION
Please notice that I'm not asking for this to become impossible, I'm just
asking for a proper optional warning and to have a way for the user to manage
the problem.
I have had this problem both using Manjaro KDE and the older Linux Mint KDE
(18.3)
--
You are receiving this mail because:
You are watching all bug changes.
