The situation is improved in gnome-pilot 2.0.14/15, but not really fixed or fixable.
IMO, it is not possible to robustly detect the correct ttyUSB port to use. The /dev/pilot symlink is the best bet, but even then I've seen situations in which it suddenly starts pointing to the wrong ttyUSB port. Last time I checked, the HAL hints weren't robust either, plausibly for the same unidentified underlying reason. At least by allowing the device name to be specified we prevent total sync failure if HAL or the udev rules get confused. The best option seem to be libusb syncing. That doesn't suffer from the ttyUSB problems. Just select 'usb:' as the device name, and it should just work (assuming you've blacklisted the visor module and installed your libusb udev rules). The pilot-link guys still consider direct libusb support as a beta feature, hence they weren't recommending that distributions dump the visor usbserial module just yet. Not sure when this is likely to change: already it seems that libusb is causing fewer problems than usbserial. At least the HAL support means we no longer have to poll sysfs. -- should automatically detect attached devices and use the apporpriate port https://launchpad.net/bugs/30015 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
