Evolution won't sync calendar with Palm

Thanks for your bug. I've forwarded the issue upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=316370

Upstream would like to get some precisions about the issue:

"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?"

and from IRC: "also, ask him to run the gpilotd from the prompt, which will spew
out messages in console"

Could you reply to these questions?

upstream would also know 'which "calendar" (personal, exchange or groupwise) was
he trying to sync?'

(In reply to comment #3)
> upstream would also know 'which "calendar" (personal, exchange or groupwise) was
> he trying to sync?'

Sorry for the delay in getting back to you. I was trying to sync w/ "personal"
calendar 1st, which didn't work. Then I created a new account, added an
appointment into Evolution (as suggested by another site to create a flag), and
tried again w/out success. I tried to open gpilotd in a terminal but I don't
know how to get a GUI (sorry, I'm a noob). I also don't know how to make a gdb
trace? If you would send me some how-to I'll try it out. I won't be back at my
computer until late tomorrow as I'll be working away from it until then.

(In reply to comment #4)

> I tried to open gpilotd in a terminal but I don't
> know how to get a GUI (sorry, I'm a noob).

run "gpilotd" from a command line so you can get the debug output here and note
what it says. Then use evolution as usual and copy between the window with the
log to bugzilla

> I also don't know how to make a gdb
> trace? If you would send me some how-to I'll try it out. I won't be back at my
> computer until late tomorrow as I'll be working away from it until then.

if it crashes:
- gdb gpilotd
(gdb) run
... crash
(gdb) thread apply all bt

Let me know if you need other precisions on this

(In reply to comment #5)
> (In reply to comment #4)
>
> > I tried to open gpilotd in a terminal but I don't
> > know how to get a GUI (sorry, I'm a noob).
>
> run "gpilotd" from a command line so you can get the debug output here and note
> what it says. Then use evolution as usual and copy between the window with the
> log to bugzilla
>
> Hi, sorry I haven't replied but I had to reinstall Breezy due to a few bugs.
Now, however, I can't get gnome-pilot to recognize my Tungsten at all. I've
followed the same procedure I used in Hoary and also in Breezy, but something's
awry. I've asked a couple other forum members who posted the same problem to
look at this bug and send you guys the error messages in the meantime. I'll get
back to you if I can get it working again. One thing I should mention is that
the name of the device in the udev rules (ubuntu guide) is not 'Palm Handheld'
for the Palm Tungsten T5, it's 'palmOne'.
> > I also don't know how to make a gdb
> > trace? If you would send me some how-to I'll try it out. I won't be back at my
> > computer until late tomorrow as I'll be working away from it until then.
>
> if it crashes:
> - gdb gpilotd
> (gdb) run
> ... crash
> (gdb) thread apply all bt
>
>
> Let me know if you need other precisions on this

(In reply to comment #2)
> Upstream would like to get some precisions about the issue:
>
> "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?"
>
> and from IRC: "also, ask him to run the gpilotd from the prompt, which will spew
> out messages in console"
>
> Could you reply to these questions?

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

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.

Latest update to gnome pilot did not solve the problem

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

(In reply to comment #10)
> It's defintely related to timezones.. I got it working... Here's what I did:

> KF

Nice work. I'd come up with a different solution by setting my ubuntu install to
use UTC time instead of local. This allowed me to use kpilot to sync my calendar
and tasks and gpilotd to sync my address book. I still got sync errors for the
calendar and tasks in evo but they worked with kpilot.... go figure.

Your solution however is much better and works like a charm. Thanks :)

(In reply to comment #10)
All we need now is Ubuntu to update pilot-link to 0.12 and full backups will
work as well without failing at the Web backup.

(In reply to comment #12)

> All we need now is Ubuntu to update pilot-link to 0.12 and full backups will
> work as well without failing at the Web backup.

pilot-link is an universe, evolution uses gnome-pilot

Are you sure the whole issue can be fixed with a new pilot-link package?

Unfortunately, I don't have the hardware, but if you could try to build and use:

http://packages.debian.org/experimental/otherosfs/pilot-link

that'd ROCK and hopefully help a lot of people.

upstream comment:

"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 have the same problem with my Palm Zire, but I can't fix the problem by adjusting Timezones, since they are already the same.
If I switch the ECalendar conduit off, everything will work fine, but the calendar is not synchronized :(

I'm also having the same problem with my Palm m515. Used to work fine. I'm not sure what changed. Attached is the gpilotd log. Is there any way to get more useful information than gpilotd-WARNING **: Synchronization failed!?

Steve.

Gpilotd crash when I sync the calendar of my Palm Tungsten E

Same problem. There's no crash, but calendar synchronisation has recently started to fail (without giving any indication of an problem). When run from the command line (with a little assistance!), the output is similar to that above (see below). Also, duplicate calendar entries appeared from the first sync onwards.

gpilotd-Message: gnome-pilot 2.0.15 starting...
gpilotd-Message: compiled for pilot-link version 0.12.3
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Watching Palmtop (usb:)

[...]

ecalconduit-Message: ---------------------------------------------------------

ecalconduit-Message: pre_sync: Calendar Conduit v.0.1.6
ecalconduit-Message: Using timezone: /softwarestudio.org/Tzfile/Europe/London

(gpilotd:5936): gpilotd-WARNING **: Synchronisation failed!

I closed the upstream bug as obsolete as its quite an old bug and the last comment was in 2years ago. if any one face this with evolution 2.30 feel free to open this bug again.