I'd like to add a few notes to this bug. I installed just the Sqlite backend as I don't want MySQL on this machine. This worked fine on squeeze and wheezy, but I recently upgraded to jessie and every time I logged into a KDE session I would get a dialog box saying that Akonadi was "upgrading resources" which would stay there for a minute or so without progress. Upon further investigation I discovered that the Akonadi server wouldn't start because it was looking for MySQL:
$ akonadictl start [...] mysqld not found. Please verify your installation [correct, it's not installed on this machine] [more error messages and a stack trace] ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error) [the above part repeats three more times] "akonadiserver" crashed too often and will not be restarted! Maximiliano Curia wrote: > akonadi-backend-mysql is the default backend, if you want to setup a > postgresql or sqlite backend you need to manually change akonadi > configuration to use that connection. Manually? Are you joking? This is KDE, not bash with more colors. > This is documented in: > /usr/share/doc/akonadi-backend-sqlite/README.Debian.gz ...which says, among other things: "Just install the backend package which is the most appropriate for your setup [...]" That's what I did. Again, if the MySQL backend is required for the package to work, why isn't there a dependency? That's what the original bug report was asking. Either Akonadi *needs* the MySQL backend, therefore a dependency is required, or the fact that Akonadi won't start without the MySQL backend is a bug that needs fixing. Just select the first available backend and be done with it. By the way, if you just write: [%General] Driver=foo ...into ~/.config/akonadi/akonadiserverrc, then the control panel will start and let you set the configuration. It's funny that an invalid configuration works better than a valid configuration without the backend. Truth be told, the real question for me is that I don't want Akonadi on my system, but it is a dependency of several core KDE packages (I didn't track which ones exactly) so it can't be removed. I "solved" the problem by dpkg-redirect'ing /usr/bin/akonadi* and /usr/lib/libakonadi out of the way, so package dependencies are satisfied. The KDE session starts without errors and every piece of KDE that I'm actually interested in runs fine, so I guess Akonadi is not really required. I have no problem if you won't fix the Akonadi package dependencies as I've now made sure it won't affect me, but I'd really like if someone fixes the other KDE packages' dependencies so I can remove Akonadi altogether. -- Ciao, Flavio Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52952c5f.2050...@stanchina.net
