Bug 324383

Summary:	Dolphin should warn about missing filesystem support
Product:	[Frameworks and Libraries] frameworks-kio	Reporter:	Alexander Nestorov <alexandernst>
Component:	general	Assignee:	KIO Bugs <kio-bugs-null>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	adawit, alexandernst, frank78ac, kdelibs-bugs-null, nate
Priority:	NOR	Keywords:	usability
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Alexander Nestorov 2013-09-02 08:57:12 UTC

Dolphin should warn users when they try to do some operations with a FS that isn't supported. For example, if ntfs-3g isn't installed and you try to write to a NTFS FS, Dolphin will show an error message saying that you're missing permissions, but the real reason is that Dolphin isn't able to write to the FS.

Main problem here is that Dolphin is confusing the user with a wrong message. Also, it would be nice to make Dolphin warn about unsupported FS. (Like Mac OS or Windows).

Reproducible: Always

Steps to Reproduce:
1. Uninstall ntfs-3g
2. Try to write/save a file to a NTFS drive
3. Error message is shown
Actual Results:  
An error shows up saying that you lack permissions, which is not true in any way.

Expected Results:  
A warning saying that ntfs-3g (or equivalent) should be installed before trying to write to the volume.

Comment 1 Frank Reininghaus 2013-09-02 21:04:43 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:32:45 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:34:49 UTC

Thanks for the quick reply.

(In reply to comment #2)
> Anyways, this has been present in *all* version since *ever*.

I assume that this includes 4.11.0, so I'll reassign to KIO.

Comment 4 Alexander Nestorov 2013-09-02 21:35:40 UTC

Yes, this includes 4.11.0 :)

Comment 5 Alexander Nestorov 2015-02-02 02:21:16 UTC

Can I get this bug in a "Confirmed" state?