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 700235 - Only shows the first of multiple GMail contacts with the same email address
Only shows the first of multiple GMail contacts with the same email address
Status: RESOLVED OBSOLETE
Product: folks
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: Unset
Assigned To: folks-maint
folks-maint
Depends on:
Blocks:
 
 
Reported: 2013-05-13 16:15 UTC by Matteo Settenvini
Modified: 2018-09-21 16:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matteo Settenvini 2013-05-13 16:15:04 UTC
Note: I am unsure about where to file this bug, as it might be instead a bug of GNOME contacts, or libgdata instead. folks sounded the more plausible culprit, but please feel free to move this bug where it pertains if it's wrong.

To reproduce this bug, please create two Google contacts inside GMail. Set different names to them, and some extra info to be able to distinguish them (for instance, a different birthday), but use the *same e-mail address* for both. This is not an uncommon scenario; a lot of families have one unique address for both spouses + children — which is exactly my scenario.

Now, if you wait for the system to sync with Google's server, and open the GNOME Contacts application, try searching for both names: only one of them will be in the list (usually, the first in alphabetical order). I found out of this issue by using gnome-shell search capabilities: I needed the street address of the second contact, and wasn't able to search for it.

It should be noted that opening evolution's address book, selecting the GMail source, and searching for both contacts behaves correctly (e.g. both contacts are found and shown separately, as expected).
Comment 1 Philip Withnall 2013-05-15 06:36:56 UTC
This is an expected behaviour of libfolks, because it implicitly links contacts which have the same e-mail address (because an e-mail address is almost always unique). We did consider the case where several members of the same family share an e-mail address, but decided it was uncommon enough to not require special support.

If you open GNOME Contacts and search for the single contact with this e-mail address, the right-hand pane should list all the personas which form it. Try clicking ‘Unlink’ next to each of them. That should fix things.

If that doesn’t work, then there’s actually a bug.
Comment 2 Matteo Settenvini 2013-05-16 09:31:49 UTC
Thanks Philip; I understand. 

However, using "unlink" does not work; I can see only one of the (in this case) two accounts that concur to all displayed information. Thus, I cannot unlink the second one, because it isn't there.

I am reopening this bug so that it's possible to unlink incorrectly merged contacts.
Comment 3 Philip Withnall 2013-05-17 13:50:31 UTC
(In reply to comment #2)
> However, using "unlink" does not work; I can see only one of the (in this case)
> two accounts that concur to all displayed information. Thus, I cannot unlink
> the second one, because it isn't there.

Hmm. That’s unexpected. Can you run gnome-contacts with the following command:
    G_MESSAGES_DEBUG=all FOLKS_DEBUG=all gnome-contacts &> contacts.log
and e-mail contacts.log to me (bugzilla@tecnocode.co.uk) please, along with the e-mail address/other identifying information of the contact which is showing the problem? Feel free to remove other personal information from the log.

Could you also e-mail me a screenshot of the erroneous contact as shown in gnome-contacts please? Again, feel free to black out any other personal information.

Thanks.
Comment 4 GNOME Infrastructure Team 2018-09-21 16:02:21 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/folks/issues/62.