[bug] carddav client running amok?

asked 2015-11-16 11:51:16 +0200

cy8aer gravatar image

updated 2015-11-19 21:47:52 +0200

I crashed my owncloud instance. I could recover my calendar but contacts are not running anymore. After that I had a drastically draining of my phone's battery. Just running top showed carddav-client is consuming ressources. I disabled my address account and rebooted but carddav-client was still on top. After deleting the calendar account and killing the carddav-client it does not restart and does not consume ressources anymore.

So it seems that carddav-client ignores disabled accounts (I could see PROFIND requests on my owncloud server till I killed the account). Is this working as designed or a bug?

[UPDATE] carddav-client still there - uses 98% cpu. How can I really get it reset?

[UPDATE2] chmod 644 /usr/lib/buteo-plugins-qt5/oopp/carddav-client - but this is not the way it should be done. Now I get a "Failed to create client plug-in: carddav" but it is not starting anymore. @jolla any fix hints? Where does carddav-client get it's configuration from? Is there any way to delete/reset this configuration?

[UPDATE3] ahem - without carddav-client running it seems to significant lower the battery draining (from 15%/night when the backend worked to 5%/night). Of course: this is subjective (one night only!) but I assume that there are other problems like the not deleted settings when removing an account.

[UPDATE4] Now I created a new owncloud instance. All things are running fine again. And while initializing the contacts I got an idea why carddav-client was running: Birthdays from contacts!

edit retag flag offensive close delete