https://bugs.kde.org/show_bug.cgi?id=323455
--- Comment #25 from Andreas Hartmetz <ahartm...@gmail.com> --- Here is the cleaner solution that I had in mind (note it doesn't need the other change). Akonadi does already wait until it has started all agents before reporting "ready", but started just seems to mean agent process or thread launched - which isn't that useful for clients who expect to see the agents on DBus. The fix assumes that that is the underlying problem and waits until all agents appear on DBus before reporting "server ready". Need to see if that assumption is correct. https://invent.kde.org/pim/akonadi/-/merge_requests/260 -- You are receiving this mail because: You are watching all bug changes.
