Bug#686147: Fixing up "no akonadi-mysql" installations

Hi, to eventually fix up akonadi startup issues after a dist-upgrade or a fresh install due to missing mysql, please manually install akonadi-backend-mysql Unfortunately there is no way to have that fixed automatically (other than making akonadi hard-depend always on mysql). Sorry for the is

Bug#686147: marked as done (akonadiserver: returned with exit code 255 (Unknown error))

Your message dated Tue, 26 Mar 2013 19:32:36 + with message-id and subject line Bug#686147: fixed in akonadi 1.7.2-3 has caused the Debian Bug report #686147, regarding akonadiserver: returned with exit code 255 (Unknown error) to be marked as done. This means that you claim that the problem

Bug#686147:

I was able to fix this by simply following the instructions in bug 580706 for manually editing the akonadi configuration file to use sqlite. If I delete the akonadi configuration file, the next time akonadi-server is run, it regenerates an akonadi configuration file with "mysql" as the database bac

Bug#686147: akonadiserver: returned with exit code 255 (Unknown error)

Package: akonadi-server Version: 1.7.2-1 Severity: normal Randomly, I am not able to execute krunner (Kde Menu -> Run command). Nothing happens. When I execute krunner in a konsole, I get the following output: david@Miho:~$ krunner QDBusConnection: session D-Bus connection created before QCor