Description of problem: When starting Kmail, immediately see: "Personal Information Management Service is starting", then the error "Akonadi Information Management Service is not operational" and cannot proceed further in Kmail. Version-Release number of selected component (if applicable): See above RPM info. How reproducible: Every time Kmail started. Steps to Reproduce: 1. Start Kmail 2. 3. Reproducible: Steps to Reproduce:
CC: (none) => maurice
N.B. This Mageia-5-Alpha1 installation is using a copy of the /home from my Mageia-4 installation. I tried the akonadiballoomigrator, which reported that 'The transition has already been done'. Are there e.g. any 'nepomuk-->baloo transition' procedures that should have been done? This problem totally prevents the use of Kmail.
After the 'dbus' update in today's s/w update, I'm glad (and relieved) to report that the Akonadi blockage has gone, and I am able to get into Kmail 4.13.2, though it took some effort to get back to normal, because (and this might not be the whole story): (1) Kmail had lost the current location of the 'local' directory, so could not find my email database. (2) Kmail had lost the whole 'POP' server setup. (SMTP server setup still intact) (3) All mail filters had to be adjusted to reflect the re-found Local folders. (4) All folder 'View' settings had been reset to default. On the positive side, KMail's 'Find Messages' seems at last to be restored to its old efficacy.
so fixed ?
This bug is probably due to mariadb server crashes reported in bug 13561. mariadb was fixed with mariadb-10.0.12-2.mga5 (2014-07-09). *** This bug has been marked as a duplicate of bug 13561 ***
Status: NEW => RESOLVEDCC: (none) => lmenutResolution: (none) => DUPLICATE
> so fixed ? Well, the problem has not recurred since a general Cauldron s/w update early July, so 'yes'!