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 738347 - Local avatars should have priority over gravatar
Local avatars should have priority over gravatar
Status: RESOLVED DUPLICATE of bug 713347
Product: geary
Classification: Other
Component: contacts
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-10-11 12:43 UTC by Nikos Roussos
Modified: 2016-09-19 04:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Nikos Roussos 2014-10-11 12:43:46 UTC 
Geary currently fetches contacts from evolution-data right? Most of my contacts have an avatar there, but Geary ignore this and searches on Gravatar instead. Although Gravatars is a nice feature, avatars from local contact list should have priority.

Currently even if a contact doesn't have a Gravatar but has a local one you get the default emtpy one.
Comment 1 Jim Nelson 2014-10-14 17:26:08 UTC 
Geary does not use EDS today for contacts.  It is something we want to implement in the future (bug #714160).  However, that ticket is for autocompleting contacts when composing a message.  We should also use the avatars from EDS as well.
Comment 2 Nikos Roussos 2014-10-15 08:50:53 UTC 
Geary currently auto-completes contacts from the Contacts Gnome app (which I added through Evolution/Carddav). Although this works fine, it seems to ingore the avatars.
Comment 3 Jim Nelson 2014-10-20 17:52:21 UTC 
Geary does not auto-complete contacts from GNOME Contacts or any other application or library.  Geary harvests email addresses from messages it downloads and stores them in its own internal contacts database.  That's how auto-complete works.
Comment 4 Michael Gratton 2016-09-19 04:49:58 UTC 

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