[SOLVED] Akonadi crashes after upgrade

[Bald Brick]

After upgrading KDE to 4.5.1 I get a number of dialogue windows when I log in to KDE.

They tell me that a couple of Akonadi resources and an Akonadi agent have crashed with segmentation faults (Signal 11).
The resources are akonadi_maildir_resource and akonadi_vcard_resource. The agent is akonadi_maildispatcher_agent.

This is not a serious problem: when I get to my desktop both the resources and the agent are running, so they've obviously been relaunched automatically. So far I have seen no ill effects of the crashes apart from the message windows, but I thought I should report this somewhere nevertheless.

If I just log out and in again I don't get the dialogues; if I reboot I do.

Some other parts of the new KDE are also a bit crash-prone, but I'll start another thread about them if they don't calm down.

[ruel24]

That's exactly the errors I was getting. I reinstalled from scratch and did a fresh update and still had a few problems, but not as many...

[ruel24]

Update: It's worse, now. I rebooted, now I have no KDE at all. I've had enough of messing with it today, I'll deal with it tomorrow. I've never had an update go wrong like this from PCLinuxOS before...

[pinoc]

On my updated system I do not have these problems. However, when I do the remaster of this working system, and then an installation of this remaster, then I get the exact same akonadi problems => no fullmonty remaster for now 
-p.

[Bald Brick]

Your situation is worse than mine, pinoc, considering all the people waiting for your remaster. And I suppose ruel's is even worse than yours. Unfortunately I'm out of ideas.

[pinoc]

updated 5 systems without any issues, including the FM (though they were no fresh installs but continued updated installations). The FM-remaster worked out fine, and the live-session of that remaster works fine as well. The problems appear only after harddrive installation, no idea why only there but it renders the remaster useless. This situation seems to correspond to ruel24's report of an update on a fresh install. Still confident that Tex will find the source of this problem 
-p.

[wedgetail]

blackbird
Any interesting error messages in the /var/log/ department?

Have no idea what Akonadi does but can it be started from konsole?

I am just in the process of moving back to a faster machine which will be running an older kde 4.4.5 without problems.  I just may let it run on till kde451 settles down.  Before turning power off here I thought I would just nip past the Forum and read a few messages.

The system I am leaving is fully updated kde451 and I have not noticed anything unusual {cross my fingers}  I don't need more problems right now   

[Bald Brick]

blackbird
Any interesting error messages in the /var/log/ department?

I glanced at a few log files, but I didn't find anything interesting -- possibly because I didn't know what I was looking for.

Have no idea what Akonadi does but can it be started from konsole?

Akonadi is supposed to handle reading, writing and querying PIM data in a consistent way. In KDE3 different programs and modules did it themselves in their own different ways. How Akonadi does it I do not know.

I tried killing the Akonadi server to see if restarting it would come up with any juicy error messages, but it was automatically restarted before I had time to do anything.

Note that even if certain Aconadi resources crash when I log in after a reboot, that doesn't bother me at all: they've also been restarted before KDE is fully up and running. The whole thing is a much more serious problem for pinoc and ruel24.

The system I am leaving is fully updated kde451 and I have not noticed anything unusual {cross my fingers}  I don't need more problems right now  

For most people the upgrade seems to have been smooth and painless.

[wedgetail]

blackbird
I am normally both feet in the pond as soon as I see something new, I had just successfully upgraded to kde451 though it was a lean test system. I was just heading back to upgrade my twin engined workhorse when I noticed a number of messages about niggles.  I will sit on the fence a little while longer 

[Texstar]

blackbird
I am normally both feet in the pond as soon as I see something new, I had just successfully upgraded to kde451 though it was a lean test system. I was just heading back to upgrade my twin engined workhorse when I noticed a number of messages about niggles.  I will sit on the fence a little while longer 

Hope it is barbed wire! buhahaha ouch my butt!

[Texstar]

Remove the kdepim and kdepim4-runtime packages and the akonadi error will go away. Until the kde developers update these packages to version 4.5.x you will have problems with kmail/kontact/kdeaddress book resources etc...

[Bald Brick]

Remove the kdepim and kdepim4-runtime packages and the akonadi error will go away. Until the kde developers update these packages to version 4.5.x you will have problems with kmail/kontact/kdeaddress book resources etc...

And decapitation would probably cure my headache....

... which in this case is a very mild one: it doesn't require many mouse clicks to make the error messages go away and after that the system works as expected. For me at least the crashes aren't a real problem; the dialogue boxes are just a bit untidy. Don't think about it.

In all other respects 4.5.1 works perfectly (if one follows your advice and updates dbus from testing).

[Texstar]

For me it only will crash on first login if akonadi doesnt exist in .config and .local folders. Once the database is created any reboots or logins does not generate a plasma crash anymore. Anyway I've patched akonadi not to crash on first login if database does not exist. I will push to repos soon. I'll be so happy when the kde developers update kdepim packages to 4.5.1.

[mikkl]

For me it only will crash on first login if akonadi doesnt exist in .config and .local folders. Once the database is created any reboots or logins does not generate a plasma crash anymore. Anyway I've patched akonadi not to crash on first login if database does not exist. I will push to repos soon. I'll be so happy when the kde developers update kdepim packages to 4.5.1.

Thanks for the all the hard work Tex!

mikkl

[Bald Brick]

For me it only will crash on first login if akonadi doesnt exist in .config and .local folders. Once the database is created any reboots or logins does not generate a plasma crash anymore. Anyway I've patched akonadi not to crash on first login if database does not exist. I will push to repos soon. I'll be so happy when the kde developers update kdepim packages to 4.5.1.

Thanks Tex!

The culprit seems to be the file ~/.config/akonadi/mysql-local.conf.

Akonadi gave me lots of error messages some weeks ago, so I uncommented the line "sql_mode=strict_trans_tables" in that file according to the instructions on the Akonadi web pages. Now I commented it again and uncommented the long line with the same beginning instead (which the KDE/Akonadi site gave as an alternative). No more crashes, touch wood.