[feisty] problems syncing todo list while the rest of the plugins work

Are you still having this problem with current Dapper?

I can't get any kind of sync between a Treo 650 and Evolution in up-to-date-as-of-today Dapper. I think there are at least two major problems:

- The Treo seems to bring the USB connection up only when synching, so there's some weird ordering bugs as to when you start the desktop software and when to start the synch on the handheld
- The Treo uses the "new" Palm protocol (I think I've seen a "version 5" thrown around) that isn't fully supported by pilot-link < 0.12.x, and might not be supported at all
- The /usr/share/gnome-pilot/devices.xml incorrectly identifies the device as a Zire 31 (same USB device ID), which may or may not be an issue

I've been able to sporadically sync using pilot-xfer, but never with gnome-pilot, and I haven't figured out a way to sync Evolution without using gnome-pilot (I'd be surprised if it existed).

A new version (2.0.14) was uploaded to Edgy. It'd be nice if you had a chance to test this and report back, if the problem still persists.

I've upgraded to edgy yesterday morning. In Dapper I only got a vague error message, now I got Bug Buddy with the attached backtrace.

gnome-pilot still only syncs the address book, but I do get an error message after the first succesful sync part.

Jacob: do you still have that issue? I think the crash was fixed already.

(This looks like a different issue to me, btw.)

Yes, I still have this problem. It might be another issue, but the symptoms are the same.
The Addressbook is synchronyzed correctly, but gnome-pilot crashes during or at ECalendar.

Jacob: does it still crash?

Yes. When I press the sync button on my Zire, the gnome-pilot progressbar appears and informs me that the EAddress starts and succesfully ends. Then it says that ECalendar starts and hangs. In the meantime two gnome-pilot settings windows open, and a Bug-Buddy window.

Just noticed: when I disable the ECalendar conduit, everything works ok. So, apparently the problem is that conduit.

I have the same problem on Edgy with a Treo 650. There's no crash, no message, simply : no synchronisation ... :)

When I launch gpilotd in console I have to message :

(gnome-pilot:15692): gpilotd-WARNING **: Synchronization failed!

Hope that can help ...

I had a similar problem as poppy.

* Treo 650 running Palm OS 5.4.8
* Ubuntu Edgy Eft 64-bit
* vendor-supplied USB cable

I added the Pilot Applet to my top toolbar, and the configuration wizard executed. When prompted to connect the device in order to fetch the user ID, nothing happend. I manually inserted the visor module (`sudo modprobe visor`), after which the applet was able to fetch the user ID and complete configuration.

One my first sync, I enabled the following conduits:
* Backup
* EAddress
* ECalendar
* EMemos
* EToDo
* File
* MemoFile
I executed a hotsync from the Palm, and it started without incident. The Evolution stuff was synchronized first with no problems. During the backup portion, the process stalled, and eventually the status window simply vanished.

No BugBuddy, no kernel messages, no meaningful log data reported anywhere.

I disabled all the conduits except Backup, and tried another sync. Things started fine, but again the backup simply stopped and the status window vanished. It stalled at a different point in the process than the first time.

I next started gpilotd manually in the console, with all the Evolution conduits activated but the backup conduit disabled. This succeeded.

I re-configured the conduits to disable everything except Backup and launched gpilotd manually in the console again. To my surprise, this worked: a full backup was executed successfully.

So I put the applet back into my toolbar and ran yet another backup. This worked successfully.

There are two problems here.

When calendar doesn't crash, but just doesn't appear to sync, you've probably got a case of:
http://bugzilla.gnome.org/show_bug.cgi?id=316370

When the caledar crashes, that looks to me like something different. It is possible that it is a regression introduced with the as-yet-unofficial port of the evolution conduit code to the pilot-link 0.12.x API. I don't know.

Everybody who has the problem: Does it crash or does it not crash?

As I said at 2006-10-12, I have a crash of the calendar conduit.

Daniel Holbach wrote:
> Everybody who has the problem: Does it crash or does it not crash?
>

For me, with a Treo 650, it hangs. (Which can be classified as a type of
crash?)

--Bruce

In my case, I was getting crashes in evolution-data-server. It would appear to be:
http://bugzilla.gnome.org/show_bug.cgi?id=319076

See also the following upstream bug:
http://bugzilla.gnome.org/show_bug.cgi?id=363102
... which contains a patch to evolution-data-server to prevent freeing of an ical data structure by a background thread while the data is in use. This seems to be the exact cause of the crashes I was getting every time with the calendar conduit.

363102 is, IMO, a dupe of 319076.

Does it still crash for anybody?

In Feisty final with a Treo 650 connected as usb: the sync for calendar, memo and contacts work, but hangs when trying to sync the To Do list from the test unit. Turning off the conduit will make things work again. The rest of the conduits will work fine even.

Flint is also having a problem with getting his palm synched...

The question I have is where is the log stored for pilot-xfer, or is there an option to turn on debugging. I really want to know about the conversation between the palm pilot and the Ubuntu process pilot-xfer.

With a casual look at things this did not jump out of a web or a man page at me. The very useful strace does not focus on the conversation. Note that I have high confidence in the "lower" ISO layers of my link. The reason is minicom. What I did was run the venerable minicom, unplugged the male rs232 cable, and while typing with one hand, shorted out pins 2&3. I knew then that I had data in my hand.

A log of what pilot-xfer was doing out the serial port would help me a lot.

Anyway, have fun in Spain. I will see you all in Boston.

Regards,

Flint