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 226408 - got many duplicate contact entries after palm sync
got many duplicate contact entries after palm sync
Status: RESOLVED DUPLICATE of bug 215724
Product: evolution
Classification: Applications
Component: Do Not Use
pre-1.5 (obsolete)
Other All
: Normal normal
: Future
Assigned To: JP Rosevear
Evolution QA team
evolution[interop]
Depends on:
Blocks:
 
 
Reported: 2002-06-18 11:44 UTC by birger
Modified: 2013-09-13 12:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description birger 2002-06-18 11:44:20 UTC
Description of Problem:
After a palm sync with gnome-pilotd there were dublicate records in the
contacts database and some of the appointments have duplicates too - next
time they have triplicates and so on...

Steps to reproduce the problem:
1. add record on palm contacts
2. hotsync
3. record is in evolution
4. hotsync

Actual Results:
2 identical records in contacts

Expected Results:
merging of records, or if records are identical: no change


How often does this happen? 
Everytime I sync there is one more record in evolution

Additional Information:
At some point all of these records ended up in my palm as well, but I
forgot under what circumstances...

With jpilot and Gnomecal/Gnomecard this never happened.
Comment 1 Fabian Fagerholm 2002-09-03 06:44:37 UTC
I'm seeing this, too - although in my case, records are correctly
displayed in Evolution (if there's supposed to be one record, then
there is one record) but they are duplicated on my Palm V. There are
never more than one additional record per erroneous record.

It may have something to do with the internal id tag of the records. I
recall having looked at the output of gpilotd while running as a
foreground process in a terminal, and there were some equality tests
running by that suggested Evolution (or the Calendar conduit, I'm not
aware of how this works internally) was looking at the record id's and
found a negative match where the match should be positive.

I can perform tests if	needed; just tell me what to do.
Comment 2 aaron 2003-04-16 20:09:37 UTC
Appears to be a dup of 15724.

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