GNOME Bugzilla – Bug 648058
Doesn't allow empty names for user defined fields
Last modified: 2011-08-31 17:32:55 UTC
Created attachment 186170 [details] Screenshot of Evolution Contacts when problem occurs I'm running the Fedora 15 64 bit beta with Evolution 3.0.0. Whenever I set-up an addressbook to be sync'd with my contacts in my Google Apps account, I do not get all the contacts and get the following error: "Unable to perform search. The backend for this address book was unable to parse this query. A required property of a <entry/gContact 'user Defined field> element (@key) was not present." Interestingly this works perfectly in Fedora 14 with Evolution 2.32.2. Also I've noted that exactly 157 contacts are sync'd with Evolution each time out of the 537 contacts I have in my Apps contacts. This has persisted over repeated installs of F15 (just due to the alpha/beta status). I can't see anything unique about the contacts that sync and those that don't. I'll be more than happy to supply additional info as needed. Thanks. Mike.
CC'ing main author of Google addressbook backend for his ideas.
What version of libgdata do you have installed? If you kill the e-addressbook-factory process and then restart it using the following command: LIBGDATA_FORCE_HTTP=1 LIBGDATA_DEBUG=3 /usr/libexec/e-addressbook-factory can you take the last few lines of output (i.e. so that the last few network requests are included) and either attach them here or e-mail them to me privately (philip@tecnocode.co.uk) please? Feel free to redact any personal data as long as you don't change the structure of the XML in the debug log. Thanks.
libgdata is version 0.8.0-2.fc15 x86_64. I'm also sending the requested output directly to Philip as a .txt file as the output generated is quite large. Please let me know if any other info is required. Thanks. Mike.
I've fixed this in libgdata. You'll have to wait until the next release of libgdata (which will be 0.8.2) is packaged on Fedora. In the meantime, you should be able to fix this by either adding names to the user defined fields you have for a couple of your contacts, or by removing those fields entirely. I've written up some more detailed instructions in a private e-mail. Fixed on master: commit 9560c55e2163e15d4b486eaadd6f9f336fa7f816 Author: Philip Withnall <philip@tecnocode.co.uk> Date: Tue Apr 19 09:13:01 2011 +0100 Bug 648058 — Doesn't allow empty names for user defined fields Allow Google Contacts' user defined fields to have empty names. Test cases updated. Closes: bgo#648058 gdata/services/contacts/gdata-contacts-contact.c | 11 ++++++++--- gdata/tests/contacts.c | 6 ++++-- 2 files changed, 12 insertions(+), 5 deletions(-) and on libgdata-0-8: commit 400a4e74f5a506ddff07605a93aa7412262fea38 Author: Philip Withnall <philip@tecnocode.co.uk> Date: Tue Apr 19 09:13:01 2011 +0100 Bug 648058 — Doesn't allow empty names for user defined fields Allow Google Contacts' user defined fields to have empty names. Test cases updated. Closes: bgo#648058 gdata/services/contacts/gdata-contacts-contact.c | 11 ++++++++--- gdata/tests/contacts.c | 6 ++++-- 2 files changed, 12 insertions(+), 5 deletions(-)
I can confirm that making the changes suggested in two contacts that had the user defined fields indeed fixed the issue. Now within Evolution 3.0.0 the addressbook is perfectly in sync with the Google Apps contacts. Thanks very much for resolving this issue! Mike
*** Bug 650050 has been marked as a duplicate of this bug. ***
647067 is duplicate of this in my case too
*** Bug 647067 has been marked as a duplicate of this bug. ***
*** Bug 653804 has been marked as a duplicate of this bug. ***