Summary: | akonadi server crashes when recreating the MySQL akonadi database | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Christoph Pospiech <pospiech-HD> |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aespejo9, iamgrief |
Priority: | NOR | ||
Version: | 5.2.0 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/akonadi/02555d1695a5b77d2ebead2a982481e1706016ef | Version Fixed In: | 16.04.2 |
Description
Christoph Pospiech
2016-05-02 09:13:18 UTC
Workaround works like a charm! Thank you so much! Git commit 02555d1695a5b77d2ebead2a982481e1706016ef by Daniel Vrátil. Committed on 15/05/2016 at 22:53. Pushed by dvratil into branch 'Applications/16.04'. Fix MySQL initialization with NO_ZERO_DATE mode We don't enable NO_ZERO_DATE by default, but external servers may be configured to use it and will fail to create the PimItemTable in such case. Having a default time on atime makes no difference since we already explicitly set atime to QDateTime::currentDateTime() in the code when appending a new PimItem. FIXED-IN: 16.04.2 M +2 -2 src/server/storage/akonadidb.xml http://commits.kde.org/akonadi/02555d1695a5b77d2ebead2a982481e1706016ef Este es el mensaje que me envía: "EL servicio de gestión de información personal de akonadi no esta funcionando" |