Summary: | KMail/Akanodi always mixes up IMAP folders | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | wuselwu <einmaladresse_2> |
Component: | IMAP resource | Assignee: | Christian Mollekopf <chrigi_1> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | kdebugs, kdepim-bugs, Martin, vkrause |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
wuselwu
2014-10-31 12:58:42 UTC
Larx, two questions: 1) What versions of KDEPIM / Akonadi have you seen this with last? 2) Did you by chance delete the database? Or change DB type from one to another, SQLite to MySQL or so? Although Akonadi should be only a cache it is *not* safe to delete the database. You will loose folder assignments that way. Also Akonadi does not migrate the database if you change to another DB type. So you will loose folder assignments on that as well. See: Bug 336581 - accidental database loss causes Akonadi / KMail to silently break correct folder assignments Thanks, Martin First, I'm glad that these bugs get finally attention! Thanks for that. But: Frankly, I don't use Akonadi any longer, as I'm sick and tired of having to worry all the time because of mysteriously lost mails, contacts and calendar items. Sounds a bit harsh, but I've been hit once to often by these bugs. However, I still follow the bug report in the hope that these bugs get fixed, as I would like to use KDE integrated PIM software... 1) I gave up on Akonadi about half a year ago. Following openSUSE tumbleweed, that must still have been a KDE4 version. 2) During the numerous times the bug apeared, I used several computers, several user accounts, did some complete re-installs, used MySQL dedicated and MySQL embedded, and so on. The bug has been there for years over several installation- and hardware-cycles. I'm a bit concerned about using Akonadi once again for reasons of bug hunting, as I'd have to use it on live PIM data, and I don't want to risk the (expected) silent data loss once again. But if there was some real chance of developper attention, I'd re-think ;). |