Discussion:
Nasty KMail/Akonadi bug
Volker Wysk
2018-10-28 06:39:06 UTC
Permalink
Hi!

I've asked for help recently with the subject "KMail badly broken". I'd like
to detail what I've learned about the cause of the problem, which has been
solved.

I'm running my own, shiny, local Dovecot IMAP server. I keep all mail in that
server (except for the trash). It works really well.

The problem seems to occur, when I configure the trash folder to be on that
server. It normally is in the "Local Folders". When I try to delete mail from
the local trash folder, the problem occurs.

Here is the problem description again, so you don't have to look in the other
message ("KMail badly broken"):

-----snip-----
I'm getting a bad error from KMail:

"Im E-Mail-Programm ist ein schwerwiegender Fehler aufgetreten. Das Programm
wird beendet. Die Fehlermeldung lautet: Could not create collection trash,
resourceId: 2"

(Translation: "In the email program, a grave error occured. The program is now
being terminated. The error message is: Could not create collection trash,
resourceId: 2")
-----snip-----

Bye
Volker
Volker Wysk
2018-10-28 06:56:20 UTC
Permalink
Post by Volker Wysk
The problem seems to occur, when I configure the trash folder to be on that
server. It normally is in the "Local Folders". When I try to delete mail
from the local trash folder, the problem occurs.
I mean, the problem occurs at every start of KMail, after trying to delete
mail from the local trash folder. And immediately afterwards, too. KMail
becomes completely unusable.

Bye
Volker
Martin Steigerwald
2018-10-28 09:49:19 UTC
Permalink
Post by Volker Wysk
I've asked for help recently with the subject "KMail badly broken".
I'd like to detail what I've learned about the cause of the problem,
which has been solved.
If you see a bug and have a clear way to reproduce it, please report it
to https://bugs.kde.org
--
Martin
Volker Wysk
2018-10-28 12:35:42 UTC
Permalink
Post by Martin Steigerwald
Post by Volker Wysk
I've asked for help recently with the subject "KMail badly broken".
I'd like to detail what I've learned about the cause of the problem,
which has been solved.
If you see a bug and have a clear way to reproduce it, please report it
to https://bugs.kde.org
It has already been reported:

https://bugs.kde.org/show_bug.cgi?id=339214

Cheers
Volker

Loading...