Version: 4.7 (using KDE 4.7.1) OS: Linux Despite of my adressbooks are all synced via groupdav resource, the FBURL (free Busy URL) in KAdressbook under the "Business" tab -> Groupware does _NOT_ sunc. Everything else is synched fine. In addition, the groupware server even returns a FBURL as part of the VCards and that information is discarded by Kabc/KAdressbook. I have to enter this information manually on every machine. Once the resource is deleted and setup later again, the FBURL information will be gone again and will hav to be reentered. Very annoying indeed. Since the whole groupdav sync works so great by now, I guess this bit is a forgotten leftover??? Reproducible: Always Steps to Reproduce: Add carddav/groupdav resource to Akonadi/KAdressbook. Let it sync. Actual Results: Contacts fine, but no FBURL information despite being sent by server. Expected Results: Contacts with the FBURL set. No only that the FBURL is not extracted from the synced VCard, even the manually entered FBURL in KAddressbook is not being written back.
Relates somewhat to the old Kabc3 bug: Bug 106140
And another one: Where is the manually entered FBURL (in KAddressbook) stored? It's not in Akonadi when I browse trough my contacts despite of being entered in KAddressbook.
And when I export my VCard with the manually added FBURL, guess what: It does not export either. So bug Bug 106140 has not been addressed in the past 6 YEARS!
And all that because it seems that vcardtool (http://websvn.kde.org/trunk/KDE/kdepimlibs/kabc/vcardtool.cpp?revision=1172275&view=markup&pathrev=1217600) still does not parse for "FBURL".
Created attachment 64278 [details] ignore-wrong bug
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.