https://bugs.kde.org/show_bug.cgi?id=230247
--- Comment #23 from Maciej Mrozowski <reavertm gmail com> 2010-10-07 00:44:31 --- Take a look at akonadi log I posted here some time ago (and what other people said as well before) - Akonadi *doesn't* crash or report *any* issue - yet self-test dialog appears - I suppose it rules out database corruptions and XDG_ issues right from the start, do you agree? The source you're interested in is in kdepimlibs as it's where Akonadi server control library is implemented (akonadi server itself just provides DBus API). Please digg there. As for why it does not happen for everyone - if I knew that it would be probably fixed already. Possible answers: race conditions or improperly or too optimistic timeouts set - so depending on machine performance. Akonadi::Control class uses timers and other workarounds to simulate synchroneous (blocking) startup/shutdown (which is otherwise natively event based). This bug has been voted by a few people and it has a few duplicates so it's quite safe to assume issue is present. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
