Bug 427929 - Have no size limit for trash by default
Summary: Have no size limit for trash by default
Status: RESOLVED NOT A BUG
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-18 14:05 UTC by Claudius Ellsel
Modified: 2020-10-19 07:05 UTC (History)
1 user (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 Claudius Ellsel 2020-10-18 14:05:40 UTC
SUMMARY
Currently as I learned, there is a size limit for the trash. To my understanding that means that files from the trash get auto deleted if the limit is exceeded?

If that is the case then that can lead to unexpected data loss. Thus I strongly suggest to have no size limit applied by default to prevent this unexpected behavior from happening.

I might be wrong with the assumption that files get deleted from trash if the limit is exceeded. Please correct me if that is the case.
Comment 1 2wxsy58236r3 2020-10-19 03:22:22 UTC
Although the default size limit for trash is 10%, the default action is "show a warning".
In other words, under default settings, oldest or largest files will not be automatically deleted even if the trash is full.

Reference:
https://invent.kde.org/frameworks/kio/-/blob/master/src/ioslaves/trash/kcmtrash.cpp
Comment 2 Claudius Ellsel 2020-10-19 07:05:45 UTC
You are right, thanks for checking. I should have checked myself before filing this :)