# how can I fix carddav after upgrade to Aurajoki?

This morning I upgraded to Aurajoki. Now my addressbook is empty :( This is really getting an annoying habbit that with every uprade one of the sync modules (caldav/carddav) starts acting up. I don't get the problem, please help.

Cheers!

edit retag close delete

So I am back to commenting my own posts. I checked the local contacts.db on my device and it looks OK; I can access the data with sqlite3 and there are lot's of phone numbers and other data.My address book is not completely gone; some numbers are available but the majority is not. all the avatars are not visible but the .jpg files are (I guess) where they are supposed to be. What now?

( 2016-09-09 00:21:47 +0200 )edit

Which contacts db are you checking? The one under the privileged directory?

Anyway, my guess is that the data remaining in the database is "locally added or modified" data, whereas the data which is now missing, is from a remote sync server. Some change in the CardDAV sync plugin may have broken support for your sync service, and depending on the type of sync error which occurred, the plugin may have resorted to a "clean sync" (i.e., roll-back and re-sync) - which, if that also failed, could leave you in your current state.

Can you provide sync logs? Steps are as follows (requires developer mode):

1) ensure that /etc/systemd/journald.conf contains RateLimitBurst=5000 and RateLimitInterval=5s and then reboot device if you had to change those

2) open ssh terminal to device, restart sync daemon with extra debugging enabled:

 systemctl --user stop msyncd
killall msyncd
MSYNCD_LOGGING_LEVEL=8 devel-su -p msyncd


3) leave that running, and open a new terminal to collect logs:

 devel-su journalctl -af | grep carddav


4) Trigger sync via Settings | Accounts -> Long-press CardDAV -> Sync.

5) After waiting ~10 seconds, it should be finished. Please email the logs from the journalctl terminal to me at chris dot adams at jolla dot com and I will investigate.

Thanks!

( 2016-09-09 03:40:58 +0200 )edit

To follow up on this sad matter. I sent @chris_adams the output from journalctl as he suggested. Hope it shows something that helps trace the cause for this bug.

The db I was mentioning in my first comment was the one in ~/.local/share/system/Contacts and it contains the list of phone numbers (and other data) that I would expect to see in the Contacts app. Dont' know if this is part of the original fs layout or if it's a backup I once made.

The db in ~/.local/share/system/privileged/Contacts just contains a hand full of numbers that were most likely added recently.

So still, any hint on solving this is greatly appreciated :) I kind of feel like back in the 80ies when every phone call was a surprise because I do not recognize the callers number ;)

Cheers

( 2016-09-11 13:36:03 +0200 )edit

So, the one in ~/.local/share/system/privileged/Contacts is the "real" database. The one in ~/.local/share/system/Contacts is what we expose to third party applications (including Android applications).

If the privileged database does indeed only contain numbers which were added recently on your phone, then the scenario I outlined (related to clean-sync failing) seems likely, but in any case I will check the logs you've sent me and investigate further. Thanks!

( 2016-09-12 06:43:06 +0200 )edit

I got kind of impatient so I tried something. I deleted the directory /home/nemo/.local/share/system/privileged/Contacts and the account I used for syncing. Then I set up a new account for syncing and initiated the first sync.

I see on the server side (owncloud) that there is a contact from my phone but nothing else happens. That seems to suggest that the sync adapter is definitely broken for syncing contacts with owncloud :(

Do I have to add that this really sucks big time?

( 2016-09-26 18:36:46 +0200 )edit

Sort by » oldest newest most voted

More a workaround than a solution, but at least I have an address book on my phone:

1. dump the contacts to a .vcf file
2. scp the file to your phone
3. import the contacts to the contacts app

Clearly this is not something that can go on forever, but it serves until the problem will have been fixed.

Cheers!

more