| Summary: | Fatal "Could not create collection outbox" following upgrade to 4.11.0, duplicate special folders, locale issue? | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Paul Gideon Dann <pdgiddie+kde> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | dilfridge, mail, pcn |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.11 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=325658 | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Paul Gideon Dann
2013-09-02 14:46:31 UTC
It turns out this was caused by a duplicate resource: I already had a resource for my local maildir (~/local/share/local-mail), and during the upgrade KMail presumably added another instance of this resource. I had previously configured my local mail folder manually, so I assume some logic decided the default local mail resource didn't exist and added it. I'm guessing the first resource to lock the mailbox caused the second to fail. This should crash, though, so I won't set to "resolved" just yet. I'll leave it here in case someone has time to do some testing to reproduce the bug and report the actual issue. This *shouldn't* crash. (Typo.) Also seen by me on Gentoo upon upgrade to 4.11. (The trick to get kmail2 running again is to remove the duplicate special local folders with akonadiconsole. That's just a workaround though.) Additional datapoints:
* I saw the problem on upgrade from 4.11rc2 to 4.11.0 (packager prerelease). kontact starts up, shows a dialog box "serious problem, program terminated: "Could not create collection Entwürfe resourceId: 9" and terminates on OK. Entwürfe is german for Drafts.
* From memory and maybe related, some of the special folders (like "Recycle Bin") were duplicated with different translations ("Papierkorb" and "Mülleimer").
I observed the same bug or at least one very similar when upgrading Kubuntu from 13.04 to 13.10 - pushing Kmail from 4:4.10.5-0ubuntu0.1 to 4:4.11.3-0ubuntu0.1. In my case it is the "sent-mail" folder, resourceId: 2 that "could not create collection". I am at loss as to what to do - I know too little about KDE configuration to figure out how to detect duplicated folders, much less to remove them. Could someone point to some helpful information, please? Oh, I forgot to mention, in my case the KMail program did not crash. It puts out a nice alert box with the error message, and an OK to click on, before the program terminates nicely. Still, it is a singularly useless error message. It talks about "collection" and "resourceId", things that have no meaning in my universe as a KMail user. The message tells me that something is not done, therefore the program terminates. But it does not at all help me in identfying, much less solving the problem. I succeeded in working around the problem - not that the problem in any way is solved. What I did was to kill me entire KDE configuration (the ~/.kde directory) and kill the akonadi (~/.local/share/akonadi and ~/.config/akonadi) - all done from a console login, so KDE itself was not active during the process. Then login again via KDE and laboriously configure all of KDE from the beginning (fortunately, I had most of it documented). My actual mail archive (in ~/.local/share/local-mail) survived (I did take a backup first!), and was accessible from my reconfigured KMail. This info above is just information that may help others that are hit by the same problem. Now some info about the problem itself: I tried to do some debugging while the problem was still manifest. I did not figure out much, the entire KMail setup is too complex for me to figure out in my spare time. I did discover the source of the report - it is thrown in kdepimlibs, in the method Akonadi::SpecialCollectionsRequestJob::slotResult. But then that is because of an error situation established earlier in some callback processing of a DBus communication - at that point I ran out of time :-) If anyone are interested in solving the basic problem - that something may happen during the 4.11 update that can render KMail useless with a useless error message - I still have a copy of my old ~/.kde - if someone are interested, I will provide copies of selected files to this bug report. But I do not know what exactly to provide, and I will not dump the entire shebang on you ... I may even be able to re-manifest the bug if I try real hard, but will not give any promises. This is really a two-tier bug - bug 1, the update creates a problem, bug 2, that problem manifests itself by throwing a far-too-lowlevel error message to the defenseless user. Wow; I don't think anything that drastic is required. You just need to have a look at your Akonadi resources. In System Settings, go to Personal Information. Look through all the resources there that are responsible for e-mail. You should have only one resource responsible for your local mail (the duplicated resources may have different names). Click "modify" on each one to see the folder that they're pointing at. For me, besides my public e-mail account, I have a resource named "Local Folders" which points to /home/<username>/.local/share/local-mail. If there are several resources that point to local folders, that is probably the cause of the problem. You should remove one of them, especially if they point to the same folder. When you remove a resource, it won't actually delete the e-mail data stored in the directory it points to. There is an easier workaround. Start akonadiconsole and look at your local folders. If you have "Duplicates" there, e.g. two times an "Outbox" or two times a "Waste bin", for example with a different localization (I've seen both "Papierkorb" and "Mülleimer" being present), delete the *empty* one. Afterwards kmail should start fine. Just happened to me too, but your workaround fixed it. 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 kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. 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. |