Bug 340224 - Empty trash does not work
Summary: Empty trash does not work
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.14.1
Platform: Debian testing Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-22 11:12 UTC by Jörg C. Frings-Fürst
Modified: 2018-01-31 16:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
trash folder before running empty (16.26 KB, image/png)
2014-10-22 11:13 UTC, Jörg C. Frings-Fürst 		Details
trash folder after running empty trash (16.41 KB, image/png)
2014-10-22 11:14 UTC, Jörg C. Frings-Fürst 		Details
trash folder after reboot (16.64 KB, image/png)
2014-10-22 11:14 UTC, Jörg C. Frings-Fürst 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jörg C. Frings-Fürst 2014-10-22 11:12:01 UTC 
After empty trash the folder seems empty. After reboot all mails are back.


Reproducible: Always

Steps to Reproduce:
1. Emtpy trash from menu 
2. reboot the computer
3. all mails are back


Expected Results:  
empty trash folder
Comment 1 Jörg C. Frings-Fürst 2014-10-22 11:13:21 UTC 
Created attachment 89247 [details]
trash folder before running empty
Comment 2 Jörg C. Frings-Fürst 2014-10-22 11:14:11 UTC 
Created attachment 89248 [details]
trash folder after running empty trash
Comment 3 Jörg C. Frings-Fürst 2014-10-22 11:14:47 UTC 
Created attachment 89249 [details]
trash folder after reboot
Comment 4 Denis Kurz 2017-06-23 19:58:24 UTC 
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 5 Denis Kurz 2018-01-31 16:53:45 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.