Summary: | Akonadi restart required to see new email in kmail | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | thatskinnywhiteguy+kde |
Component: | Gmail resource | Assignee: | Daniel Vrátil <dvratil> |
Status: | CLOSED DUPLICATE | ||
Severity: | major | CC: | dav1dblunk3tt, kde, kdepim-bugs |
Priority: | NOR | ||
Version: | 5.5.2 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
thatskinnywhiteguy+kde
2017-07-11 20:36:17 UTC
It's a little hard to be sure when exactly things stop working, but there's some evidence that suggests that the last two lines (quoted again below) indicate what's actually breaking. That is, when they're there, it seems that the email sync no longer functions. Until they appear, it seems to work properly. org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "Multiple merge candidates, aborting" org.kde.pim.akonadicore: Error during ItemSync: "Multiple merge candidates, aborting" Did this get a fix? I have a similar problem that is making kmail unusable... *** This bug has been marked as a duplicate of bug 338658 *** The duplicate this was marked as dates back to 2014. Kmail has work fine between 2014 and 2017 and this problem which was reported in 2017 and is still with us doesn't seem likely to be the original 2014 problem so I'm unmarking the duplication and reopneing. *** This bug has been marked as a duplicate of bug 338658 *** Can someone explain how a bug first reported in 2014 which did not affect me from 2014-2017 despite using gmail / kmail during this period suddenly starts to affect me during 2017/18? Unless there is some rational explanation for the 2017/18 bug to be an extant version of the 2014 bug that somehow did not cause me problems 2014-17 then this should not be marked as a duplicate of bug 338658! I doubt this was ever a duplicate of 338658. anyway for me it seems to be resolved in v5.7.3 - or at least I've managed five hours without a crash which is 4 hours more than with the last version |