Version: 4.7 (using KDE 4.7.0) OS: Linux Hi, I cannot start akonadi, it says (in KMail for example) "Akonadi personal information management service is not operational". Reproducible: Always Steps to Reproduce: Upgrade KDE to 4.7 and also KDEPIM to 4.7 and all related packages... Actual Results: Akonadi doesn't start. Expected Results: To start properly. Thanks
Created attachment 62838 [details] Akonadi test
Hi, this sounds more like an installation issue. Please check with your distribution, or the kde forums/mailing lists. (IOW : akonadi works fine for me)
usually means kdepim-runtime is not installed
Yes, but it is installed... Any other ideas? :)
I'm not a good seer self installation ? packages ? which distribution ? (if exists) content of ~/.config/akonadi/akonadiserverrc ? (if exists) content of ~/.local/share/akonadi/akonadiserver.error ?
Installed using Kubuntu installation, packages are original. I use Kubuntu 11.10 (oneiric 64bit) and still getting this error, purging ~/.kde folder doesn't help, I am nearly mad of it... Akonadiserverrc: [%General] Driver=QMYSQL [QMYSQL] Name=akonadi Host= Options="UNIX_SOCKET=/home/tom/.local/share/akonadi/socket-tom-AO722/mysql.socket" ServerPath=/usr/sbin/mysqld StartServer=true User= Password= [Debug] Tracer=null [QPSQL] Name=akonadi Host= User= Password= Port=5432 Options= StartServer=true I am adding akonadiserver.error as attachment.
Created attachment 64489 [details] Akonadiserver.error
kubuntu still uses their apparmor workaround iirc look in your dmesg output if you see some apparmor warnings or try to change: ServerPath=/usr/sbin/mysqld to ServerPath=/usr/sbin/mysqld-akonadi
I have the same problem on a fresh install of Precise. Finding it v. difficult to get anywhere.
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.