User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030507 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030507 I've seen this bug several times now, so there is a definate issue. I have several categories of addresses between my palm and my address book. For some reason, at least one of the categories will disappear fromt the address book, and appear duplicated on the palm. Reproducible: Always Steps to Reproduce: 1. Create several address books in Mozilla 2. Create addresses for them 3. Sync to palm Actual Results: 1 or more addressbooks will appear blank on Mozilla, and the entries will appear 2 or more times in the palm address book. Repeated syncing often causes data loss in the Mozilla address book, and in one case syncing causes the palm to have a Fatal error (something about the index out of bound IIRC). Expected Results: Should keep in sync so the same data exists in both locations (not duplicated) and no data loss should occour.
This has happened to me too, Palm IIIxe with palm os 3.5 and Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5a) Gecko/20030718 Seems to lose entries from the mozilla address book, and duplicate some (not all) entries on palm. First time I synced, most stuff seemed to go over ok, problems have occured subsequently. Has now left both AB very messy!
Wondering if we can get this fixed before Thunderbird ships with Palm Sync?
I saw this happen as well. I was deleting contacts on my palm address book to get rid of a bunch of duplicates, and doing occasional syncs. I also deleted cards from my mozilla address book and sync'ed. I'm not sure which operation was responsible, but I suspect it was the former.
Assignee: cavin → bienvenu
this should fix duplicates getting created on the palm - the code that checked for dups on the palm was broken.
David, If that works, your the king. This bug is bothering the living (choice word for Feces) out of me.
Attachment #140996 - Flags: superreview?(mscott) → superreview+
fixed on trunk and m4 branch
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.