Bug 313083 - Deleting 'last search' folder destroys the messages listed from the system
Summary: Deleting 'last search' folder destroys the messages listed from the system
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.9.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-11 15:45 UTC by Peter H Nancarrow
Modified: 2017-01-07 22:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter H Nancarrow 2013-01-11 15:45:49 UTC
Having had a persistent 'Last Search' folder I decided to delete it, and the pop-up window assured me that if I did delete the folder, the listed messages would still continue to exist in their original locations.  I therefore deleted the folder, but found that the original messages had been deleted also.  This has happened twice now.  For your information, my Linux platform is PCLinuxOS 2013 running on a desktop PC.

Reproducible: Always

Steps to Reproduce:
1. Implement search
2. Close KMail2, and re-start
3. Delete 'last search' folder
Actual Results:  
As described above

Expected Results:  
Should  have deleted the search results folder, but left the original messages intact.
Comment 1 David Faure 2016-07-12 07:53:12 UTC
Hello.

Were they really deleted, or was it rather that folders disappeared from the folder tree, but after restarting kmail everything was back? That would be bug 349789, which I just fixed. Please advise so we know what to do with this report.
Comment 2 Denis Kurz 2016-09-24 17:54:32 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:08:48 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.