After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 681572 - Unable to modify google contact information
Unable to modify google contact information
Status: RESOLVED DUPLICATE of bug 675712
Product: folks
Classification: Platform
Component: e-d-s backend
git master
Other Linux
: Normal normal
: Unset
Assigned To: folks-maint
folks-maint
Depends on:
Blocks:
 
 
Reported: 2012-08-10 03:06 UTC by Mark Edgington
Modified: 2012-08-22 23:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mark Edgington 2012-08-10 03:06:29 UTC 
I have tried using gnome-contacts with google, and can view the different google contacts I have.  When I make any attempt to change either the field type (e.g. Home->Work for a phone number) or a field value (e.g. 555-1212 -> 444-2121), the following error is printed to stdout:

(gnome-contacts:32614): GLib-CRITICAL **: g_source_remove: assertion `tag > 0' failed

(gnome-contacts:32614): eds-WARNING **: edsf-persona-store.vala:2078: Error in address book view query: GDBus.Error:org.gnome.evolution.dataserver.AddressBook.InvalidQuery: Invalid request URI or header, or unsupported nonstandard parameter: Exactly one of non-empty rel, label is required for phone number.

It seems not to matter which contact I am trying to edit -- I always get the above error messages, and then the contact's info reverts to what it was before I tried to edit it.

Let me know if any further information is needed...
Comment 1 Alexander Larsson 2012-08-20 14:16:37 UTC 
This seems like a folks issue.
Comment 2 Philip Withnall 2012-08-22 23:16:13 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 675712 ***