Bug 324384 - Dolphin should warn about impossible actions on certain FS
Summary: Dolphin should warn about impossible actions on certain FS
Status: RESOLVED DUPLICATE of bug 198772
Alias: None
Product: kio
Classification: Unmaintained
Component: general (show other bugs)
Version: 4.14.1
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-02 09:07 UTC by Alexander Nestorov
Modified: 2018-05-03 21:43 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Nestorov 2013-09-02 09:07:52 UTC
Dolphin should warn about some operations that aren't supported by the FS. For example, copying a 8GB file to a FAT32 drive will always fail (because FAT32 can't handle such a big file), so instead of trying to copy it, Dolphin should halt the action, explaining why it can't be done.

Another example: Some FS don't support some characters in the file name (NTFS doesn't support ¿?/ and a few others, EXT* doesn't support /). Dolphin should warn about such unsupported characters instead of writing them (as writing them may cause volume soft-failure, another OS not being able to read the volume, or any other bugs).



Reproducible: Always

Steps to Reproduce:
1. Copy a +4GB file.
2. Paste to a FAT32 volume
3. Error
Actual Results:  
Dolphin fails after copying ~4gb of the file

Expected Results:  
Dolphin should halt the operation instead of trying to do it (as it will fail always)
Comment 1 Frank Reininghaus 2013-09-02 21:04:08 UTC
Thanks for the bug report, but I think that this belongs to KIO (the library that handles moving/copying files for us).

If this issue is still present in Dolphin 4.11.0 or later (please *never* file bug reports without providing the version), just let us know, and we can reassign the report.
Comment 2 Alexander Nestorov 2013-09-02 21:31:50 UTC
Yes, perhaps KIO is better.
Anyways, this has been present in *all* version since *ever*. I mean, that bug (and the other one that I reported right after this one) have been present in (at least) KDE since 1.0
Comment 3 Frank Reininghaus 2013-09-02 21:36:27 UTC
Thanks for the quick reply.
Comment 4 Alexander Nestorov 2013-09-02 21:37:02 UTC
No problem ;)
BTW, this includes 4.11.0 too
Comment 5 Alexander Nestorov 2015-02-02 02:21:02 UTC
Can I get this bug in a "Confirmed" state?
Comment 6 Nate Graham 2018-05-03 21:43:19 UTC

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