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 499584 - Integration with Pidgin, creating dupe contacts
Integration with Pidgin, creating dupe contacts
Status: RESOLVED DUPLICATE of bug 320316
Product: evolution
Classification: Applications
Component: Contacts
unspecified
Other All
: Normal minor
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-11-25 18:49 UTC by Jon Pastore
Modified: 2009-05-03 19:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Jon Pastore 2007-11-25 18:49:08 UTC
By default Evolution is set to periodically sync contact information with Pidgin. It's creating new contacts for screen names and ICQ numbers I have in Pidgin in Evolution. The sync functionality should be checking the IM field in the contacts before creating a new contact. For example I have a contact John Doe with a screen name of kewldude12345. I now have a contact for John Doe and in the IM field it says kewldude12345 and I now also have a contact for kewldude12345.

Also if it could push contact information back to Pidgin that would be handy. Or source Pidgin libraries directly to integrate Pidgin into evolution for 1 stop messaging needs instead of running 2 applications that I run anyway. 

Other information:
Comment 1 Martin Mai 2008-12-22 11:46:52 UTC
Thank you for taking time to report this bug. Someone also reported this bug in launchpad (https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/235250).

Last comment:
>> Even worse than not checking for current contact is the fact that the newly
>> created contacts as soon as modified become unsynced and yet another contact
>> is created.

http://bugzilla.gnome.org/show_bug.cgi?id=340390 is related to this, but not the same.
Comment 2 C de-Avillez 2009-05-03 19:45:56 UTC

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