> There has always been a human-level timing
> issue when using pilot-link with a USB device:
> you need to press the button on the cradle
> first, then start pilot-link before the USB device
> disconnects.
Actually, gpilotd and gnome-pilotd did *not* have any human-level timing issues in 5.10 -- they worked fine every single time.
> The issue of this bug report appears more like
> a hang that occurs after pilot-link or gnome-pilot
> establishes the connection with the device.
If you look at the thread, this bug report covers both the occasional hang as well as more frequent time-outs.
Robert,
> There has always been a human-level timing
> issue when using pilot-link with a USB device:
> you need to press the button on the cradle
> first, then start pilot-link before the USB device
> disconnects.
Actually, gpilotd and gnome-pilotd did *not* have any human-level timing issues in 5.10 -- they worked fine every single time.
> The issue of this bug report appears more like
> a hang that occurs after pilot-link or gnome-pilot
> establishes the connection with the device.
If you look at the thread, this bug report covers both the occasional hang as well as more frequent time-outs.