Bug 451483 - dolphin trash cleanup after x days does nothing
Summary: dolphin trash cleanup after x days does nothing
Status: RESOLVED DUPLICATE of bug 205854
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: Trash (show other bugs)
Version: 5.92.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-14 08:06 UTC by Peter Ries
Modified: 2022-03-25 15:52 UTC (History)
3 users (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 Peter Ries 2022-03-14 08:06:12 UTC
SUMMARY
***
Dolphin does not clean up files in trash although cleanup after 1 day has been set.
***


STEPS TO REPRODUCE
1. current settings: cleanup after 1 day, limit size to 1% (~ 9GB here), trash full: delete oldest
2. delete some files, trash has still much capacity left, but does not seem to matter
3. wait two days and still find the files that IMHO should have been cleaned up

OBSERVED RESULT
files stay in trash

EXPECTED RESULT
really delete, cleanup up from trash 1 day after deletion

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3
Kernel Version: 5.16.14-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD RENOIR

ADDITIONAL INFORMATION
Have observed this behaviour on Kubuntu on my older laptop, too for a longer time but did not pay attention and used "autotrash" instead.
Comment 1 Peter Ries 2022-03-14 08:13:42 UTC
just found https://bugs.kde.org/show_bug.cgi?id=205854

this is what happens here, too. Putting a new file to trash and older files are gone. 

Al least confusing to user. May be scheduling "something" in the background once a day to trigger cleanup would not confuse users anymore...
Comment 2 Nate Graham 2022-03-25 15:52:44 UTC

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