[Bug 38574] Re: Pb syncing treo 650 on dapper drake

[Franz A. Heinsen]

Matt,  I just saw your question (I assume it was addressed to me -- my name is spelled with a "z", not "k").  

As of right now, with the latest Dapper Beta packages, only the usual two /dev/ttyUSB* are being created when I hit the sync button, and they disappear normally afterwards.  I don't know if more than two ttyUSB* were being created prior to upgrading to the latest packages.

In any case, syncing still takes a couple of tries, though I'm no longer getting the "invalid pointer" error when it doesn't work; instead, the daemon just keeps trying to communicate with the Treo.  Here's a snip from the log:

*** gpilotd log ***
gpilotd-Message: setting PILOTRATE=115200

(gnome-pilot:17104): gpilotd-WARNING **: pi_accept_to: Connection timed out

(gnome-pilot:17104): gpilotd-WARNING **: pi_accept_to: timeout was 3 secs
gpilotd-Message: setting PILOTRATE=115200

(gnome-pilot:17104): gpilotd-WARNING **: pi_accept_to: Connection timed out

(gnome-pilot:17104): gpilotd-WARNING **: pi_accept_to: timeout was 3 secs

... [these messages keep getting repeated until I interrupt the daemon.]

***

At least now I'm been able to stop the daemon with a normal kill i.e. without having to send it a SIGKILL.  As before, syncing suddenly works fine after a couple of tries.

-- 
Pb  syncing treo 650 on dapper drake
https://launchpad.net/bugs/38574