Summary: | Crash on startup if a trash folder is missing | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Jürgen Starek <juergen> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | christian.gonzalez, montel |
Priority: | NOR | ||
Version: | 4.12.3 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jürgen Starek
2014-03-17 10:13:58 UTC
I can't reproduce and I can find this message "kmail could not create collection trash"" in source code. The error message comes from Akonadi, see akonadi/server/src/handler/create.cpp . However, I still think that this is a bug in kmail insofar as kmail does not inform the user that they should go to the Akonadi console, nor does kmail offer the user a possibility to correct the account settings. Regarding reproducibility, perhaps we need to go into more details about the account. I'm using an IMAP account from Zimbra here, but don't know what people in the original report (bug 255104) were using. I suggest, however, that bug 255104 should be reopened, and will gladly assist in creating a reproducible scenario. Hm, maybe had the same problem. I used dolphin, right-clicked on a file->Actions->Send as email attachment -> Kmail opens the compose dialog, and stops with the message (German) "Im E-Mail-Programm ist ein schwerwiegender Fehler aufgetreten. Das Programm wird beendet. Die Fehlermeldung lautet: Could not create collection trash resourceId: 3" After starting kmail freshly without using this dolphin context menu (maybe it then creates the trash resource?) the context menu from dolphin works without problems first, then after a few starts, kmail (without parameters) does not start any more, stops with error messave above. I am Using Kubuntu 13.10, with an IMAP kmail account (server at edis.at). Trash folder is user configured here too. 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. 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. |