https://bugs.kde.org/show_bug.cgi?id=361157
S. Bryant <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from S. Bryant <[email protected]> --- Possibly related: After performing the same upgrade on Leap, I'm seeing "The Akonadi personal information management service is not operational" in any program that uses Akonadi, but I haven't seen this particular crash. It was working before the upgrade, and the Leap install was a fresh one, not an upgrade, so no generations old data to deal with. After running "akonadictl fsck" it's still "not operational". Running "akonadictl stop" doesn't stop anything. The MySQL instance was up - at least the Workbench connected to it (and complained about a MySQL version mismatch). If somebody can confirm that the combination FW5.20/Plasma5.6/Qt5.6 is known to work for Akonadi, we may be able to narrow it down to either a local configuration problem or a distribution-specific problem. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
