Bug 264872 - After deleting a folder (Local Maildir) a message appears (Unable to update collection. No such collection)
Summary: After deleting a folder (Local Maildir) a message appears (Unable to update c...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-30 18:46 UTC by Michael Jansen
Modified: 2017-01-07 22:20 UTC (History)
5 users (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 Michael Jansen 2011-01-30 18:46:15 UTC
Version:           unspecified
OS:                Linux

When deleting a local maildir folder with kmail2 the msaage "kmail folders: updating local collection failed: No such collection" appears from knotify.

Reproducible: Didn't try

Steps to Reproduce:
Delete a folder in a local maildir. 

Actual Results:  
Message appears

Expected Results:  
No message appears.

The folder is correctly deleted btw. (Checked with ls in Maildir folder ).
Comment 1 Michael Jansen 2011-01-30 18:49:15 UTC
It was reproducible for me btw. with three folder.
Comment 2 Laurent Montel 2011-07-27 11:51:00 UTC
Do you have still this bug ?
Comment 3 Michael Jansen 2011-07-27 11:55:39 UTC
Yes. Just tried. Created a folder, put 2 Messages in it and the deleted it again. 

I got 3 Notifications

- Maildir: Updating local collection failed: No such collection.
- Maildir: Cannot remove emails from folder (2x)
Comment 4 Tim Haegele 2012-01-11 14:21:53 UTC
When I delete a folder from an IMAP Account I get the notify: 

"IMAP-Konto 1: Failed to delete the folder, restoring folder list."

Creating and folder works, deleting it not. 


KMail 4.8 rc2
Comment 5 Michael Reiher 2013-07-10 22:10:47 UTC
(In reply to comment #3)
> Yes. Just tried. Created a folder, put 2 Messages in it and the deleted it
> again. 
> 
> I got 3 Notifications
> 
> - Maildir: Updating local collection failed: No such collection.
> - Maildir: Cannot remove emails from folder (2x)

Still getting the same 4.10.4. 

Just deleted a folder with maybe a 1000 mails from a local maildir.
- getting "Cannot remove emails from folder" for every single mail
(where each notification itself takes quite some CPU and outputs a bling)
- it takes forever (well, this might actually be the tons of notifications playing through)
- got another message in between the other messages: something like "resource not available". I could really read it that quick.

Pretty painful process...
Comment 6 Michael Reiher 2013-07-11 17:23:39 UTC
Correction s/4.10.4/4.10.5

Thinking about it there seem to be actually two problems:
1. Why does kmail give an error at all? Did really someting fail? Should it really present an error to the user?
2. In general, Kmail shouldn't report an error for each and every mail on operations affecting possibly thousands of mails.
Comment 7 Rigo Wenning 2013-10-03 17:23:16 UTC
(In reply to comment #4)
I can not delete folders from my imap account. (kmail2 4.11.2) but I do not get any error message. Debuggger in akonadiconsole says: 
AgentBase(akonadi_imap_resource_0): Failed to delete the folder, restoring folder list.
if I erase the thing on the server via shell, I get later:
AgentBase(akonadi_imap_resource_0): Select failed, server replied: A000646 NO Mailbox does not exist, or must be subscribed to.

If at least I would know where to erase those locally...
Comment 8 Denis Kurz 2016-09-24 17:54:54 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 9 Denis Kurz 2017-01-07 22:20:12 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.