kpilot usb device name through libusb or symlink?

[Joacim Haglund]

Binary package hint: kpilot

I have used kpilot before with my treo 600 and got it to communicate by setting the device to '/dev/ttyUSB1'. Now (in feisty) I had to set the device to 'usb:'. This I did after reading '/usr/share/doc/libpisock9/README.libusb.gz'. After reading this README, it seems reasonable, but it was kind of hard to figure out. In the help ("Handbook") it said /dev/pilot and searching around, some also suggest /dev/ttyUSB*, but none of those symlinks are created on my system when I press the hotsync button.

Version: KPilot 4.9.0 (deepsix)
Version: pilot-link 0.12.2
Version: KDE 3.5.6
Version: Qt 3.3.7

[Chris (chris-pm)]

I've also come across the same problem with Tunsten T3 syncing through usb with Feisty (KPilot/GPilotd). The default directory setting of /dev/pilot does not exist, only usb: got things working again.

[Rich Johnson (nixternal)]

Confirming due to response, plus I was able to reproduce this issue until switching to /dev/ttyUSB0. After speaking with Adrian, we believe this issue lies within the Kernel more than it does KPilot. The kernel, along with the Visor kernel module, used to report it as /dev/pilot, but have since changed. I will try and confirm that and move accordingly.

[Rich Johnson (nixternal)]

Ahh, I found it, this is a udev issue and has been reported. I will make this as a duplicate, as this is no longer a kdepim issue.