Created attachment 398558 [details] emerge --info output for my system After upgrading to mysql-5.6 both akonadi failed to start. My akonadi uses the default configuration, an internal MySQL database. I tried deleting the akonadi database .local/share/akonadi (which is only a cache), but it still would not start. Investigation shows a known issue with using the obsolete system variable "table_cache" in mysql.conf. Renaming this to "table_open_cache" fixed the problem with akonadi. However, please note that I had deleted mysql.conf (it was in the database directory) and akonadi had recreated it from scratch, but still using the obsolete variable name. Later, I found a similar problem with digikam, also configured to use an internal MySQL database. Its mysql.conf also used table_cache. However, renaming it was not enough to get digikam to start. It turns out it also uses "log_slow_queries", which needs to be renamed to "slow_query_log". With both changes, digikam starts. Again, deleting mysql.conf causes digikam to recreate it with the obsolete variable names. IMHO this is really an upstream problem, but it may make sense to patch the programs to save newcomers hitting the problem. Steps to reproduce On a system with akonadi or digikam installed and using >=dev-db/mysql-5.6 for their internal database, delete (or rename out of the way) .kde4/share/apps/digikam/mysql.conf or .local/share/akonadi/mysql.conf, and try starting akonadi or digikam. They won't start. Correcting the system variable names in the newly-created mysql.conf files will enable them to start.
Could this be bug #530012 ?
No, it's not bug #530012, though I think I recognize that from akonadi problems I had earlier. If that's the same, it's worth deleting (or renaming) mysql.conf from the akonadi directory, and any local overrides (possibly in .local, I forget). That causes akonadi to write a new (simpler) mysql.conf. That won't work either, but it's now 'cos of the renamed system variables in THIS bug! So editing by hand should be a working bypass.
As there are no more cc's on the bug i guess the bug can be closed.
