Bug 148454 - Trash system: not effective on mounted partitions
Summary: Trash system: not effective on mounted partitions
Status: RESOLVED DUPLICATE of bug 76380
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
: 320392 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-08-02 18:40 UTC by Maciej Pilichowski
Modified: 2019-12-06 19:07 UTC (History)
4 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2007-08-02 18:40:16 UTC 
Version:            (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs

I just tried to delete file (i.e. move it to Trash) -- it was virtually impossible since the computer is not so fast, and the file was big and on mounted partition (not /home/).

Note that the user in such case is forced to omit KDE somehow since there is no obvious (I know it) method to skip the Trash.

General wish -- please improve it.

My ideas:
* create trash for user on-fly on "external" partition
* make it configurable what to do -- i.e. small files can be copied to local Trash, but the bigger should only be moved to external Trash
* make possible to differentiate mounted (static) partitions and removable (like pen-drives)
* make Trash configurable what to do if there is no space to get any new deleted files
Comment 1 Steffen 2019-02-06 06:21:28 UTC 
*** Bug 320392 has been marked as a duplicate of this bug. ***
Comment 2 Robert Killingsworth 2019-07-04 19:06:43 UTC 
Same problem on Arch. I delete a file on any of my NTFS partitions and it moves it to the trash folder in my home folder. Takes forever and wastes space. Should create a .Trash or .Trash-<uid> on the drive it's deleting on and move it there.
Comment 3 Nate Graham 2019-12-06 19:07:08 UTC 

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