Seems to me that it's akonadi that is failing to shut mysqld down properly when it is running 5.5 that is causing the issue - possibly with lack of database migration to 5.6?
There's a separate crash bug in mysqld that should be fixed (it shouldn't segfault no matter what really), but I'll add a task back for akonadi as it is the akonadi package that needs to keep affairs in ~/.local/share/akonadi/ in order. ** Also affects: akonadi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1437846 Title: akonadi mysql 5.6 crash with signal 11 Status in akonadi package in Ubuntu: New Status in mysql-5.6 package in Ubuntu: Incomplete Bug description: Vivid changed mysql version recently to 5.6. Akonadi won't start anymore because mysql crash - log attached. I wanted to install a mysql dbg package but couldn't find the right one. I would like to provide more information but can't think of any valuable for now. akonadi test log is all good MySQL server is executable. Details: MySQL server found: /usr/sbin/mysqld Ver 5.6.23-1~exp1~ubuntu4 for debian-linux-gnu on x86_64 ((Ubuntu)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1437846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp