Summary: | app-office/akonadi-server: didnt start with dev-db/mysql-5.5.32 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | vylaern <vylaern> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | adaptee, franz.trischberger, genzilla, jlp.bugs, vylaern |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://projects.kde.org/projects/kdesupport/akonadi/repository/revisions/13876b14c5b6791f174918cda9d7fedb826237e6 | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=474952 https://bugs.kde.org/show_bug.cgi?id=319016 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
vylaern
2013-06-27 10:32:51 UTC
Did you resolve the MySQL problems mentioned in the forum thread yet? It looks like that's why akonadi fails to start. I order to access you mail you could try temporarily disabling akonadi (it is only a cache and does not store the actual mail). (In reply to Michael Palimaka (kensington) from comment #1) > Did you resolve the MySQL problems mentioned in the forum thread yet? It > looks like that's why akonadi fails to start. I have no idea what to do now. I did downgrade mysql to 5.5.31 and reemerged QtCore and Akonadi Server - still problem. I did the same for mysql to 5.5.32 and reemerged QtCore and Akonadi Server - the same. I did remove entire Akonadi configuration, but did not help. ~/.local/share/akonadi/ ~/.config/akonadi/ ~/.kde4/share/config/akonadi* > I order to access you mail you could try temporarily disabling akonadi (it > is only a cache and does not store the actual mail). How to do this? I am not certain if this is the same issue, but in bug #474952 a fix was committed[1]. Could you please try syncing the tree and rebuilding mysql? [1]: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/mysql-cmake.eclass?r1=1.16&r2=1.17 (In reply to Michael Palimaka (kensington) from comment #3) > I am not certain if this is the same issue, but in bug #474952 a fix was > committed[1]. Could you please try syncing the tree and rebuilding mysql? > > [1]: > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/mysql-cmake. > eclass?r1=1.16&r2=1.17 Many thanks! I have found a sollution on our forum: Rename table_cache to table_open_cache table_cache is deprecated since MySQL 5.1.3 (released in Nov. 2005) and was completely removed in MySQL >= 5.6 https://bugs.kde.org/show_bug.cgi?id=319016#c2 I forgot to add, those changes above I did in file: ~/.local/share/akonadi/mysql.conf. Re-opened, this is fixed with version =app-office/akonadi-server-1.10 which is not released yet. (In reply to Johannes Huber from comment #6) > Re-opened, this is fixed with version =app-office/akonadi-server-1.10 which > is not released yet. Ignore my last commet, its a bug in the eclass *** This bug has been marked as a duplicate of bug 474952 *** (In reply to Johannes Huber from comment #7) > (In reply to Johannes Huber from comment #6) > > Re-opened, this is fixed with version =app-office/akonadi-server-1.10 which > > is not released yet. > > Ignore my last commet, its a bug in the eclass > > *** This bug has been marked as a duplicate of bug 474952 *** The forum thread suggests that it is NOT due to the missing symbolic link, but due to the deprecated mysql function. (In reply to Franz Fellner from comment #8) > (In reply to Johannes Huber from comment #7) > > (In reply to Johannes Huber from comment #6) > > > Re-opened, this is fixed with version =app-office/akonadi-server-1.10 which > > > is not released yet. > > > > Ignore my last commet, its a bug in the eclass > > > > *** This bug has been marked as a duplicate of bug 474952 *** > > The forum thread suggests that it is NOT due to the missing symbolic link, > but due to the deprecated mysql function. I hit the same issue and a tree sync and mysql rebuild helped. I didnt change anything about configuration or rebuild akonadi-server. So i assume akonadi-server upstream has a internal check which mysql version is used and use the appropiate mysql function, which in my theory leads to the confusing output when the mysql server cant be started. |