Comment 8 for bug 569601

Hi Stefano,
My problem is that I haven't been able to reproduce this yet. My 10.04 setup works fine.
Did this break when upgrading from an earlier version of Ubuntu, or when upgrading packages? Any idea?

Here's some more info that might be helpful to narrow this down:
  Which gnome-pilot, gnome-pilot-conduits and evolution-common packages do you have?
  If you use "gpilotd-control-applet", do you see any conduits showing up in the conduits tab?
  Have you enabled the backup conduit, for example?
  Can you launch gpilotd in a terminal window, attempt a sync, and attach your terminal output to this bug?
  Does your PDA support bluetooth, or wifi? If so, you should try bluetooth or network connectivity.
  (long shot) Have you tried setting the USB timeout to zero in the config applet?
  (long shot) Have you tried starting gpilotd just before attempting to sync?

There are two odd things in the initial console output reported: it doesn't look like gnome-pilot found any conduits, and it seemed to have an error connecting to the PDA. The first problem suggests a badly built gnome-pilot package (but what's different on my system?) and the second problem suggests problems with the USB connection code, probably in pilot-link, which is why starting gnome-pilot just before you try to sync is worth a try, as that's more like the way pilot-xfer uses the underlying pilot-link USB code.