I installed kaddressbook and imported (via akonadiconsole) my google contacts. Now it crashes as soon as I launch it.
[Bug: https://bugs.kde.org/show_bug.cgi?id=353326]

I created a new user and kaddressbook works fine.
I went back to my user, uninstalled every akonadi related thing, deleted all akonadi related folders and files but it still crashes.

I deleted everything related to akonadi and kontact in:
~/.config/akonadi
~/kde/share/config/...

Am I missing some file that could be storing some settings?

BTW: If I am a regular user who wants to use kmail and his google contacts: am I forced to (figure out that I have to) install a (beta version) of akonadiconsole and figure out my way from there?

Which version of PIM are you using? Depending on the version, the configuration files may be elsewhere. You may want to use "akonadiconsole" to remove the "contact resource" you just created.
OTOH, if you could install debug symbols and provide the backtrace through the crash assistant, it would be great.

1.
I am using kmail 5.0.2 (I don't know how to get PIM's version).

2.
I did use akonadiconsole to remove all akonadi related resources, prior to reinstallation, but it didn't make any difference.

3.
I did try to report the bug, but it says that it is a duplicate of:
https://bugs.kde.org/show_bug.cgi?id=353482
But even if it is, I would like to try to figure out if it still derives from adding a google account, since, if does, kdepim is useless to me until the bug is fixed.

If all else fails, you may want to also kill the Akonadi database, which lives in ~/.local/share/akonadi.

That helped me narrow down the problem.
Kaddressbook works fine until I add my Google Account
(which basically means that KDE PIM is useless for anyone with a gmail account until this gets fixed).

Thanks for the hint.

Did you file a bug with the backtrace of the crash? Otherwise there are close to zero chances to get this fixed.

einar wrote:Did you file a bug with the backtrace of the crash? Otherwise there are close to zero chances to get this fixed.

I did.
Thanks for suggesting it, though.