GNOME Bugzilla – Bug 316370
Evolution won't sync calendar with Palm
Last modified: 2018-07-02 10:32:33 UTC
This bug has been opened here: https://bugzilla.ubuntu.com/show_bug.cgi?id=15466 "I was syncing my Palm Tungsten T5 w/ evolution (Calendar, Contacts, ToDo, Backup, etc...) under Hoary and it worked flawlessly. Since I've switched to Breezy Preview, my T5 sync's w/ evolution but only my Contact's and Backup. Calendar won't sync most importantly. I browsed the forums and it seems other's are running into this problem as well. All my conduits are set correctly in Evolution and my Palm. I set up my gnome-pilot w/ the Ubuntuguide and the Wiki for the Palm Zire (same process I used w/ Hoary)."
Have you got gpilotd messages? What exactly happens when you try to sync calendars? Any crash? Can you attach a gdb trace if it is a crash?
I'm seeing this behaviour too, in my case running debian/testing. Console output from gpilotd: etodoconduit-Message: --------------------------------------------------------- etodoconduit-Message: pre_sync: ToDo Conduit v.0.1.6 etodoconduit-Message: ToDo Conduit v.0.1.6 etodoconduit-Message: Using timezone: UTC (gpilotd:31914): gpilotd-WARNING **: Synchronization failed! backupconduit-Message: ToDoDB not modified since last sync (if you can tell me how to generate a backtrace, I'll try that)
new comment on the distro bug: "I have the same problem with my Tungsten e2 Ouput from console when synching ------------------------------------------------------------------------------------- gpilotd-Message: HotSync button pressed, synchronizing pilot gpilotd-Message: Pilot ID is 1000, name is GrantsPilot, owner is grant gpilotd-Message: Pilot has 0 entries in restore queue gpilotd-Message: Pilot has 0 entries in conduit queue eaddrconduit-Message: --------------------------------------------------------- eaddrconduit-Message: pre_sync: Addressbook Conduit v.0.1.2 eaddrconduit-Message: Current URI file:///home/grant/.evolution/addressbook/local/system (file:///home/grant/.evolution/addressbook/local/system) eaddrconduit-Message: doing fast sync eaddrconduit-Message: for_each_modified beginning eaddrconduit-Message: no events eaddrconduit-Message: post_sync: Address Conduit v.0.1.2 eaddrconduit-Message: --------------------------------------------------------- ecalconduit-Message: --------------------------------------------------------- ecalconduit-Message: pre_sync: Calendar Conduit v.0.1.6 ecalconduit-Message: Using timezone: UTC (gpilotd:8832): gpilotd-WARNING **: Synchronization failed! etodoconduit-Message: --------------------------------------------------------- etodoconduit-Message: pre_sync: ToDo Conduit v.0.1.6 etodoconduit-Message: ToDo Conduit v.0.1.6 etodoconduit-Message: Using timezone: UTC (gpilotd:8832): gpilotd-WARNING **: Synchronization failed! gpilotd-Message: Synchronization ended gpilotd-Message: setting PILOTRATE=57600 (gpilotd:8832): gpilotd-WARNING **: pi_accept_to: Connection timed out (gpilotd:8832): gpilotd-WARNING **: pi_accept_to: timeout was 2 secs"
new distro comment: "I suspect that the problem may be to do with the way Evolution time zones are being transferred to the palm, hence causing the sync failure The log from my pilot show UTC being used instead of the local time zone. Using KPilot I have been able to get calendars to sync into evolution and korganizer. However the appointment and task times are all out of whack and transfer incorrectly from evolution ( +10 hrs) where as they transfer correctly from korganizer."
distro comment: "It's defintely related to timezones.. I got it working... Here's what I did: 1) Started with a 'clean' Evolution Client (ie no appointments, contacts, etc.) 2) Launch Evolution and Choose Edit->Preferences->Calendar and Tasks 3) Set Timezone equal to New York (This is also my timezone on Palm) 4) Set up Sync and Conduits as usual using System->Pref->Palm OS Devices 5) Sync'd. Net, only real difference is I made sure my timezones were set the same between Palm and Evolution... BTW, if it matters, my device is a Palm LifeDrive KF"
That workaround works for me too! (Palm V / Evolution from deb-unstable)
This is fixed in current Head. However, I am just trying to figure-out what is the right-thing to do when timezones are different. Should I convert to target-timezone during sync?
I'm trying to track down how to fix this for ubuntu (edgy). As far as I can tell the conduit is failing on the call to: e_cal_get_changes, although since that function hasn't been modified in 10 months I assume the problem is occurring elsewhere. I've had a look through the evolution-patches archives but I haven't been able to determine which patch is fixing this problem. Would anyone be able to give me any more information about where the problem/solution is. Thanks. Steve.
I have exactly the same problems (All works fine except for syncing the calendar). I have both evolution and my palm set to the same timezone but that doesn't help :-(. Who has a suggestion how we can solve this?
Any update when the fix can be pushed? I know about 5 affected people.
I have this problem. The error I get is: ecalconduit-Message: pre_sync: Calendar Conduit v.0.1.6 ecalconduit-Message: Using timezone: /softwarestudio.org/Olson_20011030_5/Europe/London (gpilotd:15956): gpilotd-WARNING **: Synchronisation failed! Any update on a fix? This is a real bind for me. I'm considering a Palm SyncML client, a funambol server and then Evolution SyncML (which I hope doesn't have the same problem!).
Its quite an old bug report I think it should now be closed as obsolete or wont fix (if it does not work).
Closing as obsolete as there has been no activity for a quite a few years.
Well, with Evolution 2.28.3 (Ubuntu 10.04), this bug is still present. I get exactly the same error message as Comment 11. Could it be possible to re-open this bug ?
Moving to gnome-pilot. The evo conduits are no longer part of the Evolution code base. This is definitely still occurring with recent evo and gnome-pilot 2.32.0.
gnome-pilot is not under active development anymore and has not seen code changes for seven years. Its codebase has been archived: https://gitlab.gnome.org/Archive/gnome-pilot/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.