Comment 62 for bug 688576

tl;dr
change fstab to defaults,uid=1000,umask=077

Apparently I believe this is not a bug, but inteded behaviour ?

For some people who stumble upon on ntfs-3g filesystem and in my case, dolphin, doesn't seem to use the "intended" .Trash / .Trash-1000 partition, and after looking at journalctl, I see something

`Nov 11 23:13:15 ruby kdeinit5[23435]: kf5.kio.trash: Root trash dir "/mnt/Master/.Trash" exists but didn't pass the security checks, can't use it`

and looking at the error in google doesn't get me anywhere rather then other logfile, but it also has the source code, this is where i get it

https://code.woboq.org/qt5/kf5/kio/src/ioslaves/trash/trashimpl.cpp.html#1185

and according to that the .Trash and .Trash-1000 have some specification (differ on both), but generally
- it should be owned (.Trash-1000) or writeable by user (.Trash)
- it should be a dir
- its not a symlink
- it should have permission of 700 (.Trash-1000) OR have sticky bit (.Trash)

the last thing is probably constraining dolphin so it cant use the folder, and to my knowledge, we cant chmod the mounted fstab ntfs folder (?), so at least the workaround for now is to have permission of 700 on fstab.

I dont know why there's a little of this "error" in google, it seems today many people have dual drive like me with SSD main and data in HDD, and they didnt have the problem ? or is it just "us" with some special case ?