GNOME Bugzilla – Bug 662786
Google contacts have a persistent invalid cache in 3.2.1 after upgrade from 3.2.0
Last modified: 2012-03-27 11:40:35 UTC
Currently running 3.2.1-0ubuntu1. I suspect after the recent upgrade from 3.2.0, my Google contacts are not loading completely due to a cache issue. My refresh is set to 1 minute (and has been for some time, across reboots). This is my default addressbook, accessed via SSL and used for contact birthdays (all options checked in properties). Evolution only appears to load 1839 of my 1925 contacts (as shown online). Previously I noted the loaded contacts matched in Evolution to the Online total shown as "All Contacts" at google.com/contacts. The notable impact/observation, which is how I noticed this issue and related it to the recent upgrade, is that some of my co-workers emails no longer auto-complete as they did previously. I ran a debug session LIBGDATA_FORCE_HTTP=1 LIBGDATA_DEBUG=3 /usr/lib/evolution/e-addressbook-factory 2>&1 | tee eds_111026.txt during which I executed some adds and removes from the Google interface. As expected, within a minute the changes appeared in evolution. I also observed those changes in the factory output, but noted it had not downloading any other contacts during the session, thus appeared to be operating off cache. Next I purged .cache/evolution/addressbook and reloaded evolution. After re-load I received a series of "Detailed error message: Timeout was reached" errors. Without restart, I then proceeded to disable and re-enable via Online contacts to correct the timeout problem. This crashed my evolution. Upon restart my contacts now appear fine and back to normal without missing data. It seems that perhaps a cache-purge during upgrade might solve this problem. Another solution, and possibly a good enhancement, would be to allow the "refresh" of contact "cache" data in the properties where the refresh interval is specified.
I can't reproduce this problem using my 3.2.0 backup and can't rule out a crash affecting the state of the cache. Assuming it was caused by a crash during contacts load, I still beleive there is an issue as there was no indication of a problem and it seems reasonable that the client should know it does not have all the contacts at the end of the refresh interval.
I think I saw a similar bug report, about Google cache having issues.
(In reply to comment #2) > I think I saw a similar bug report, about Google cache having issues. Bug #660383?
(In reply to comment #3) > (In reply to comment #2) > > I think I saw a similar bug report, about Google cache having issues. > > Bug #660383? Yup, that might be it. I think I saw some about deleted contacts not being deleted in evolution's cache after evolution's start too, but that might be just my poor memory.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 660383 ***