Comment 68 for bug 282491

Ok. In my previous test (with the error dialog pop-up), the visor module was loaded, the serial radio button was pressed and the device name was devpilot. I just tried with this setup - the visor module was loaded, the USB radio button was pressed and the device name was /dev/ttyUSB1 - this WORKED. I synced twicw to make sure. Next I removed the visor module and the sync failed. Thus the visor module MUST be loaded for this to work.

Thanks for the help getting this far - I'll use this method until "usb:" is less buggy. I still would like for it to work the "right" way, namely "usb:", if only to make Ubuntu a more "ready for the masses" OS and will stand ready to try any other tests. Thanks again.

----------------
Ed,
I'm not clear whether you triedconfiguring gnome-pilot with "usb" radio button selected and a device entry set to "/dev/ttyUSB1" instead of "usb:"? If you can use ttyUSB1 for jpilot you should be able to use it for gnome-pilot. There may be some other bug at work, but that's definitely worth trying.

The problem is that there are two ways of connecting to palms under linux: either via a serial tty emulation ("visor" module, ttyUSBn devices) or directly via libusb (no "visor" module, "usb:" pilot-link device). The bug I'm trying to flag is that your device needs a specific 'tweak' in the libusb code in pilot-link's libpisock so that it speaks correctly to the clie.