Bug 248222

Summary: Move to trash should handle ntfs, vfat file systems by creating .trash there itself
Product: [Frameworks and Libraries] frameworks-kio Reporter: Mohd Asif Ali Rizwaan <maarizwan>
Component: TrashAssignee: David Faure <faure>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bugseforuns, claudius.ellsel, kdelibs-bugs, nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:

Description Mohd Asif Ali Rizwaan 2010-08-18 10:20:36 UTC
Version:           4.4 (using KDE 4.5.0) 
OS:                Linux

using ntfs(-3g), I use ntfs in a dual-boot dual-os (windows xp and archlinux/kubuntu), as an "Access point" for my files which i need them in all of my os. Hence, I use ntfs partition as a 'downloading', 'backup' area which can be access by all the OSes.

But, when I want to delete a file (move to trash to be exact), dolphin/kde tries to move a file from ntfs filesystem to linux file system in ~/.trash (or wherever).

it's okay with small files, but with huge files like dvd isos or video files, the move operation to ext4 file system *slows* the system down. And the *purpose* of *move*to*trash* is lost when the files themselves can't be stored in it's native partition quickly!


Reproducible: Always

Steps to Reproduce:
1. create ntfs filesystem/partition
2. mount and put a few big files there
3. using dolphin choose, move to trash (press delete key)
4. we can see that kio trash is trying to copy the files to Linux filesystem's trash folder.


Expected Results:  
kio trash, should create .trash folder (if possible with hidden attribute to hide in windows/non-native filesystem) in ntfs/vfat file system itself.

move to trash should move the files to .trash in the non-native/native filesystem considering the users' permission.

Perhaps this is also applicable for other fs like xfs, zfs, reiserfs, etc..

thank you.

OS: Linux (i686) release 2.6.35-ARCH
Compiler: gcc
Comment 1 Claudius Ellsel 2020-08-05 12:03:29 UTC

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