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 647067 - Unable to synchronize Google address book with Evolution
Unable to synchronize Google address book with Evolution
Status: RESOLVED DUPLICATE of bug 648058
Product: evolution
Classification: Applications
Component: Contacts
2.32.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
evolution[google]
Depends on:
Blocks:
 
 
Reported: 2011-04-07 17:03 UTC by Carlos
Modified: 2011-06-04 07:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
e-addressbook debug output (2.14 KB, application/x-gzip)
2011-04-17 21:49 UTC, Ian B. MacDonald
Details

Description Carlos 2011-04-07 17:03:37 UTC
Using Ubuntu 11.04 beta, using evolution for e-mail client. Unable to set a Google contact address book. No problems with e-mails (IMAP), or calendar (Google Calendar).
Comment 1 Matthew Barnes 2011-04-07 17:28:28 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Comment 2 Ian B. MacDonald 2011-04-17 20:10:21 UTC
Do you have a large number of contacts?  If so, this is probably this timeout issue that appears in Evolution 2.32 on Ubuntu 11.04

https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/755043 

Matthew, perhaps you can help resolve this issue. I have no issue with large Google contacts in evo 2.30 on Ubuntu 10.10.  

Google contacts works fine with small addressbooks (I have successfully tested one with a dozen emails) on 11.04, which is probably how this one slipped through initial testing.
Comment 3 Ian B. MacDonald 2011-04-17 21:49:29 UTC
Created attachment 186166 [details]
e-addressbook debug output
Comment 4 Ian B. MacDonald 2011-04-17 21:56:20 UTC
Attached above is debug from my e-addressbook-factory. It fails in the same place consistently. I captured this using LIBGDATA_DEBUG=3 /usr/lib/evolution/e-addressbook-factory

I've obfuscated sensitive details with XxXxXxX, or a comment bounded by this string.

It just outputs "Bye" on the console and in the GUI I see "Timeout Reached". (Next attached screenshot).

Another commenter downstream notes: "Ok, the problem here seems to be, after looking at the code, that the google backend only returns the list of contacts when it has retrieved them all, so the DBus call from Evolution to evolution-data-server times out."

https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/755043/comments/4

The messages at the start of the debug output showing an error removing non-empty directories when "Migrating local backend data" is not related and was resolved after doing some manual cleanup.  No impact to this Google contacts issue.  Interested parties can see details here:

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/761068
Comment 5 Ian B. MacDonald 2011-04-28 22:05:42 UTC
Also seeing this problem using the Evolution 3.0 packages currently present in the Debian/experimental leading me to believe this problem was not corrected in 3.0.  Same observations as noted in the downstream bug report. 

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/761068
Comment 6 Ian B. MacDonald 2011-05-05 06:43:15 UTC
So what's the next step...would a test google account with 1000 fake contacts help?
Comment 7 Ian B. MacDonald 2011-06-03 20:52:46 UTC
Turns out this is the same issue as https://bugzilla.gnome.org/show_bug.cgi?id=648058
Comment 8 Philip Withnall 2011-06-04 07:38:39 UTC
(In reply to comment #7)
> Turns out this is the same issue as
> https://bugzilla.gnome.org/show_bug.cgi?id=648058

Thanks for sorting this out.

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