Summary: | akonadictl fsck : item has no RID | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Milian Wolff <mail> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | abone27, auxsvr, ianseeks, j-kde_bts, kde, Martin, mfraz74+kde |
Priority: | NOR | ||
Version: | GIT (master) | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Milian Wolff
2012-11-03 13:00:39 UTC
Still happening in 2016 with the latest software Still happening in 2017. Still happening in 2018 :-) :-( Confirmed with Akonadi 17.08.3. Please see Bug 360834 - no mechanism to reattempt to store items without rid (just in db) into the resource and the thread akonadictl fsck: What messages indicate real issues and what to do about them? https://marc.info/?l=kdepim-users&m=149426877926602&w=2 (I am about to reply to this thread with a mail with more findings and more references to bugs report about akonadictl fsck I newly created.) for the best information on these messages I got so far. So far I am not aware of any fix, so you could only attempt to fix it up manually. Which for me is no viable option considering that I have >3000 of these messages with a local maildir resource. |