then relax. If I had a large and friendly font, I’d probably also write “Don’t panic”, on the back side of this post.

Your data is safe.

The filter works, too, and the bug is in Akonadi, but just in the tree item view, to be precise. This means that you can expect to see it again as soon as akonadi is fixed, and none of your contacts data is harmed.

To be even more specific, the bug where this is tracked is this one: https://bugs.kde.org/show_bug.cgi?id=252145

Please note that this only affects KAddressBook tree visualization, and in no way it compromises how the other application work (or visualize your contact data).

So, now that you’re more relaxed about this issue, here comes the howto part of the post:

Infact, in case you still badly need your contacts back, today I pushed a commit which (cleanly) workarounds this problem. To get it, you should do a number of things. Please note that while this procedure has worked for me like a charm, it could not work for you for many unknown reasons. Therefore, please proceed with extreme care!

1. Perform a full sync, so that all of your contacts data is backed up on the server.
2. Checkout the 0.2.x branch from git.

   git clone git://gitorious.org/akunambol/akunambol.git

3. Compile the branch as explained here (look at the section “Building Akunambol”)
4. Stop Akonadi, remove (or just backup) the local contacts, and start Akonadi again. (warning: ./local/share/contacts is where all of your contacts are stored! you might want to mv it instead)

   akonadictl stop
   rm -r .local/share/contacts/
   akonadictl start

5. Now, remove all the cache created by Akunambol. This will ensure that Akunambol won’t think that you just deleted all of your contacts (thus deleting them from the server too) but instead will think that it has just started on an empty addressbook (thus filling it with the data you saved during Step 1).

   rm -rf .kde4/share/apps/akunambol

6. Start Akunambol, and start a sync. Once it finishes you should see all of your contacts in KAddressBook again.

To close this post, yes, I know that all this procedure is a bit cumbersome, but again, if you have had this problem, don’t panic: your data is safe. You don’t need to follow these steps. You will not be able to display it correctly for the moment, but it’s only in THAT particular visualization, and all the functionality works nonetheless, including contacts searching, and other views of your contact list. Then, in case KAddressBook is really crucial to you, and you can’t afford to wait for the bugfix, you can simply use the procedure I illustrated above and everything should be fine. But actually, most of the users (me included) won’t even notice the problem…

Anyways… That’s all for now! Happy syncing! :)

In this post I’d also like to point out to you about an extremely valuable tool, written by one of my KDE co-hacker and good friend Paolo Capriotti.

I just noticed he blogged about it, I tried it this afternoon when he first shown his prerelease to me, and I must say it really rocks. It’s a tool written in ruby which performs similar tasks than kapptemplate (see kdesdk), but it works with templates and it’s *way* more powerful. It’s written for KDE 4 so that’s also a big plus (meaning automatic generation of CMake file, etc…). =)
It also comes with very handy tools builtin, and does *much* more than just generate empty apps, like it has the ability to add a GPLv2 header license to multiple source files with a one liner command line, or the ability to create skeletons for classes just as simply. Here’s the link to his blog entry:
http://pcapriotti.wordpress.com/2007/11/19/skema-01/

If you’re a developer, you should definitely try it out, it’s at its first release (0.1) after 2 days of developement, but it’s already awesome, and worths the trying. I’m already pretty excited about it. =)