Bug 16762 - Akonadi: "Multiple merge candidates, aborting"
Summary: Akonadi: "Multiple merge candidates, aborting"
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-15 23:25 CEST by Vincent D
Modified: 2018-04-28 18:58 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Vincent D 2015-09-15 23:25:28 CEST
Due to some error in the management of e-mails, in some circumstances the Akonadi infrastructure can regularly emit the following notification: "Multiple merge candidates, aborting" (twice every thirty seconds in my case).

The bug is described in:
https://bugs.kde.org/show_bug.cgi?id=338658

and is solved in the comment 39:
https://bugs.kde.org/show_bug.cgi?id=338658#c39

The Akonadi maintainers advise to poke the distribution mainteners, thus my request for an update of kdepim libraries.
Comment 1 David Walser 2015-09-16 23:19:53 CEST
Thanks for the report.  Assigning to the KDE maintainers.

CC: (none) => lmenut
Assignee: bugsquad => mageia

Samuel Verschelde 2016-08-25 16:25:26 CEST

Assignee: mageia => kde

Luc Menut 2016-08-25 16:43:01 CEST

CC: lmenut => (none)

Comment 2 Marja Van Waes 2018-04-28 18:58:01 CEST
Hi Vincent,

Thank you for having taken the needed time to report this issue!

We regret if this issue didn't get fixed in Mageia 5.

Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

I assume this bug doesn't exist in Mageia 6 or later, because KDE and its tools are entirely different there.

Closing as OLD.

CC: (none) => marja11
Resolution: (none) => OLD
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.