It all sounds like a timing issue. There have been several reports of regressions with minor udev updates, etc. It would be interesting if someone was able to report back with their experience of disabling HAL (see comment dated "2006-10-19 13:52:30 UTC") and/or libusb syncing.
It should be possible to build in an appropriate pause between HAL notification and gpilotd attempting a sync, but we need to have more of an idea of where the timing problem lies first. It would also be good (as per my previous comment) to see if the device lock-ups can be reproduced with 'pilot-xfer -t 2', by starting pilot- xfer first and then attempting a sync. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
