JM
Judd Montgomery
Mon, Aug 10, 2026 3:59 PM
I thought you said pilot-xfer worked on /dev/ttyUSB1. If so, then you can set that preference in jpilot. We can try to figure out why "usb:" doesn't work.
Judd
On 8/10/26 09:20, Ulf Zibis wrote:
Yes, I could go back to 2.0.2-1, but I prefer to use the new version.
What is missing, that it doesn't sync?
-Ulf
Am 10.08.26 um 15:08 schrieb Judd Montgomery:
sudo apt install jpilot=2.0.2-1 worked for me.
On August 10, 2026 8:39:47 AM EDT, Judd Montgomery
judd@jpilot.org
wrote:
About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
On August 10, 2026 8:31:06 AM EDT, Ulf Zibis
Ulf.Zibis@CoSoCo.de
wrote:
Hi Judd,
thanks.
-
So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
-
But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
Regards,
-Ulf
Am 10.08.26 um 12:49 schrieb Judd Montgomery:
Hi Ulf,
Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
Judd
On August 10, 2026 4:22:01 AM EDT, Ulf Zibis
Ulf.Zibis@CoSoCo.de
wrote:
Jpilot mailing list --
jpilot@lists.jpilot.org
To unsubscribe send an email to
jpilot-leave@lists.jpilot.org
Jpilot mailing list --
jpilot@lists.jpilot.org
To unsubscribe send an email to
jpilot-leave@lists.jpilot.org
Jpilot mailing list --
jpilot@lists.jpilot.org
To unsubscribe send an email to
jpilot-leave@lists.jpilot.org
Jpilot mailing list --
jpilot@lists.jpilot.org
To unsubscribe send an email to
jpilot-leave@lists.jpilot.org
I thought you said pilot-xfer worked on /dev/ttyUSB1. If so, then you can set that preference in jpilot. We can try to figure out why "usb:" doesn't work.
Judd
On 8/10/26 09:20, Ulf Zibis wrote:
> Yes, I could go back to 2.0.2-1, but I prefer to use the new version.
> What is missing, that it doesn't sync?
>
> -Ulf
>
> Am 10.08.26 um 15:08 schrieb Judd Montgomery:
>
>> sudo apt install jpilot=2.0.2-1 worked for me.
>>
>> On August 10, 2026 8:39:47 AM EDT, Judd Montgomery
>> [<judd@jpilot.org>](mailto:judd@jpilot.org)
>> wrote:
>>
>>> About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
>>>
>>> You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
>>>
>>> On August 10, 2026 8:31:06 AM EDT, Ulf Zibis
>>> [<Ulf.Zibis@CoSoCo.de>](mailto:Ulf.Zibis@CoSoCo.de)
>>> wrote:
>>>
>>>> Hi Judd,
>>>>
>>>> thanks.
>>>>
>>>> 1. So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
>>>>
>>>> 2. But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
>>>>
>>>> Regards,
>>>>
>>>> -Ulf
>>>>
>>>> Am 10.08.26 um 12:49 schrieb Judd Montgomery:
>>>>
>>>>> Hi Ulf,
>>>>>
>>>>> Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
>>>>>
>>>>> Judd
>>>>>
>>>>> On August 10, 2026 4:22:01 AM EDT, Ulf Zibis
>>>>> [<Ulf.Zibis@CoSoCo.de>](mailto:Ulf.Zibis@CoSoCo.de)
>>>>> wrote:
>>>>
>>>> ---------------------------------------------------------------
>>>>
>>>> Jpilot mailing list --
>>>> jpilot@lists.jpilot.org
>>>> To unsubscribe send an email to
>>>> jpilot-leave@lists.jpilot.org
>>>
>>> ---------------------------------------------------------------
>>>
>>> Jpilot mailing list --
>>> jpilot@lists.jpilot.org
>>> To unsubscribe send an email to
>>> jpilot-leave@lists.jpilot.org
>>
>> _______________________________________________
>> Jpilot mailing list --
>> jpilot@lists.jpilot.org
>> To unsubscribe send an email to
>> jpilot-leave@lists.jpilot.org
>
> _______________________________________________
> Jpilot mailing list --
> jpilot@lists.jpilot.org
> To unsubscribe send an email to
> jpilot-leave@lists.jpilot.org
UZ
Ulf Zibis
Mon, Aug 10, 2026 7:23 PM
The older version 12.5 or 13.0 worked with /dev/ttyUSB1, sometimes only with /dev/ttyUSB2, don't know why, but I still had to add the visor module.
The new version 15.0 doesn't need the module.
JPilot 2.1.0-2 works with nothing:
Abgleich mit /dev/ttyUSB1
Hot-Sync Knopf jetzt drücken
pi_bind error: /dev/ttyUSB1 Datei oder Verzeichnis nicht gefunden
Check your sync port and settings
Exit-Status: SYNC_ERROR_BIND
Fertig.
Abgleich mit /dev/ttyUSB2
Hot-Sync Knopf jetzt drücken
pi_bind error: /dev/ttyUSB2 Datei oder Verzeichnis nicht gefunden
Check your sync port and settings
Exit-Status: SYNC_ERROR_BIND
Fertig.
-Ulf
Am 10.08.26 um 17:59 schrieb Judd Montgomery:
I thought you said pilot-xfer worked on /dev/ttyUSB1. If so, then you can set that preference in jpilot. We can try to figure out why "usb:" doesn't work.
Judd
On 8/10/26 09:20, Ulf Zibis wrote:
Yes, I could go back to 2.0.2-1, but I prefer to use the new version.
What is missing, that it doesn't sync?
-Ulf
The older version 12.5 or 13.0 worked with /dev/ttyUSB1, sometimes only with /dev/ttyUSB2, don't know why, but I still had to add the visor module.
The new version 15.0 doesn't need the module.
JPilot 2.1.0-2 works with nothing:
=====================
****************************************
Abgleich mit /dev/ttyUSB1
Hot-Sync Knopf jetzt drücken
****************************************
pi_bind error: /dev/ttyUSB1 Datei oder Verzeichnis nicht gefunden
Check your sync port and settings
Exit-Status: SYNC_ERROR_BIND
Fertig.
****************************************
Abgleich mit /dev/ttyUSB2
Hot-Sync Knopf jetzt drücken
****************************************
pi_bind error: /dev/ttyUSB2 Datei oder Verzeichnis nicht gefunden
Check your sync port and settings
Exit-Status: SYNC_ERROR_BIND
Fertig.
===========================
-Ulf
Am 10.08.26 um 17:59 schrieb Judd Montgomery:
> I thought you said pilot-xfer worked on /dev/ttyUSB1. If so, then you can set that preference in jpilot. We can try to figure out why "usb:" doesn't work.
>
> Judd
>
> On 8/10/26 09:20, Ulf Zibis wrote:
>
>> Yes, I could go back to 2.0.2-1, but I prefer to use the new version.
>> What is missing, that it doesn't sync?
>>
>> -Ulf
UZ
Ulf Zibis
Tue, Aug 11, 2026 8:14 PM
This is not enough. I had to do:
sudo apt install libpisync1=0.13.* libpisock9=0.13.* libpisock-dev=0.13.* pilot-link=0.13.* jpilot-plugins=2.0.2-1 jpilot=2.0.2-1
sudo apt-mark hold libpisync1 libpisock9 libpisock-dev pilot-link jpilot-plugins jpilot
Now JPilot syncs again with the long known crash at the end:
[....]
freeing plugin list
Fertig.
unlock succeeded
command=100 [Fertig.
]
sync child exiting
command=105 [
]
address_gui_cleanup()
jp_pref_write_rc_file()
jp_pref_write_rc_file()
caught signal SIGCHLD
Getötet
It's a pity, that version 2.1.* is unusable.
Hopefully you find the source of the problem.
Thanks,
Ulf
Am 10.08.26 um 15:08 schrieb Judd Montgomery:
sudo apt install jpilot=2.0.2-1
This is not enough. I had to do:
sudo apt install libpisync1=0.13.* libpisock9=0.13.* libpisock-dev=0.13.* pilot-link=0.13.* jpilot-plugins=2.0.2-1 jpilot=2.0.2-1
sudo apt-mark hold libpisync1 libpisock9 libpisock-dev pilot-link jpilot-plugins jpilot
Now JPilot syncs again with the long known crash at the end:
[....]
freeing plugin list
Fertig.
unlock succeeded
command=100 [Fertig.
]
sync child exiting
command=105 [
]
address_gui_cleanup()
jp_pref_write_rc_file()
jp_pref_write_rc_file()
caught signal SIGCHLD
Getötet
It's a pity, that version 2.1.* is unusable.
Hopefully you find the source of the problem.
Thanks,
Ulf
Am 10.08.26 um 15:08 schrieb Judd Montgomery:
> sudo apt install jpilot=2.0.2-1
JM
Judd Montgomery
Tue, Aug 11, 2026 8:29 PM
I think if you connected on /dev/ttyUSB1 then you have the visor module
loaded. Try rmmod visor.
I see a connection on usb:, not ttyUSB1.:
$ pilot-xfer -l -p usb:
Listening for incoming connection on usb:... connected!
...
Judd
On 8/10/26 09:17, Ulf Zibis wrote:
Ah, ok. I did:
$ sudo modprobe -r usbserial visor
modprobe: FATAL: Module usbserial is in use.
Now I can connect without visor, but only via -p /dev/ttyUSB1, not via usb, libusborusb:Is there another name or shortcut which can work? But I coudn't removeusbserial`.
===================
ich@W541:~$ pilot-xfer -p usb -l
Unable to bind to port: usb
Please use --help for more information
ich@W541:~$ pilot-xfer -p libusb -l
Unable to bind to port: libusb
Please use --help for more information
ich@W541:~$ pilot-xfer -p usb: -l
Listening for incoming connection on usb:... ^C
ich@W541:~$ pilot-xfer -p /dev/ttyUSB1 -l
Listening for incoming connection on /dev/ttyUSB1... connected!
Reading list of databases in RAM...
AddressingLibRecent-HsCh
MyTreoCASData
ADD053enUSSData
[......]
-Ulf
Am 10.08.26 um 14:39 schrieb Judd Montgomery:
About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
On August 10, 2026 8:31:06 AM EDT, Ulf Zibis Ulf.Zibis@CoSoCo.de wrote:
Hi Judd,
thanks.
-
So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
-
But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
Regards,
-Ulf
I think if you connected on /dev/ttyUSB1 then you have the visor module
loaded. Try rmmod visor.
I see a connection on usb:, not ttyUSB1.:
$ pilot-xfer -l -p usb:
Listening for incoming connection on usb:... connected!
...
Judd
On 8/10/26 09:17, Ulf Zibis wrote:
> Ah, ok. I did:
> $ sudo modprobe -r usbserial visor
> modprobe: FATAL: Module usbserial is in use.
>
> Now I can connect without `visor`, but only via `-p /dev/ttyUSB1`, not via `usb`, libusb` or `usb:`
> Is there another name or shortcut which can work?
> But I coudn't remove `usbserial`.
>
> ===================
> ich@W541:~$ pilot-xfer -p usb -l
> Unable to bind to port: usb
> Please use --help for more information
>
> ich@W541:~$ pilot-xfer -p libusb -l
> Unable to bind to port: libusb
> Please use --help for more information
>
> ich@W541:~$ pilot-xfer -p usb: -l
>
> Listening for incoming connection on usb:... ^C
> ich@W541:~$ pilot-xfer -p /dev/ttyUSB1 -l
>
> Listening for incoming connection on /dev/ttyUSB1... connected!
>
> Reading list of databases in RAM...
> AddressingLibRecent-HsCh
> MyTreoCASData
> ADD053enUSSData
> [......]
> ====================
>
> -Ulf
>
> Am 10.08.26 um 14:39 schrieb Judd Montgomery:
>> About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
>>
>> You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
>>
>> On August 10, 2026 8:31:06 AM EDT, Ulf Zibis <Ulf.Zibis@CoSoCo.de> wrote:
>>
>>> Hi Judd,
>>>
>>> thanks.
>>>
>>> 1. So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
>>>
>>> 2. But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
>>>
>>> Regards,
>>>
>>> -Ulf
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
JM
Judd Montgomery
Tue, Aug 11, 2026 8:33 PM
Hi Ulf,
I hope we figure it out also. I can't reproduce it and I don't
understand what is wrong so I can't fix it. I thought you were syncing
fine with /dev/ttyUSB1.
On a stock XUbuntu 26.04 box I needed to add this file.
$ cat /etc/udev/rules.d/60-palm.rules
Palm handhelds — libusb access for pilot-link (pilot-xfer -p usb:)
SUBSYSTEM=="usb", ATTR{idVendor}=="0830", MODE="0660", GROUP="plugdev",
TAG+="uaccess"
With these permissions
$ ls -l /etc/udev/rules.d/60-palm.rules
-rw-r--r-- 1 root root 158 Aug 9 23:09 /etc/udev/rules.d/60-palm.rules
and then run "sudo udevadm control --reload-rules && sudo udevadm
trigger" to load it.
NOTICE that the usb rule specifies the group "plugdev", NOT dialout.
With this you'll need to be in the plugdev group, which seems to be more
modern than "dialout".
$ pilot-xfer -l -p usb:
Listening for incoming connection on usb:... connected!
Judd
On 8/11/26 16:14, Ulf Zibis wrote:
This is not enough. I had to do:
sudo apt install libpisync1=0.13.* libpisock9=0.13.* libpisock-dev=0.13.* pilot-link=0.13.* jpilot-plugins=2.0.2-1 jpilot=2.0.2-1
sudo apt-mark hold libpisync1 libpisock9 libpisock-dev pilot-link jpilot-plugins jpilot
Now JPilot syncs again with the long known crash at the end:
[....]
freeing plugin list
Fertig.
unlock succeeded
command=100 [Fertig.
]
sync child exiting
command=105 [
]
address_gui_cleanup()
jp_pref_write_rc_file()
jp_pref_write_rc_file()
caught signal SIGCHLD
Getötet
It's a pity, that version 2.1.* is unusable.
Hopefully you find the source of the problem.
Thanks,
Ulf
Am 10.08.26 um 15:08 schrieb Judd Montgomery:
sudo apt install jpilot=2.0.2-1
Hi Ulf,
I hope we figure it out also. I can't reproduce it and I don't
understand what is wrong so I can't fix it. I thought you were syncing
fine with /dev/ttyUSB1.
On a stock XUbuntu 26.04 box I needed to add this file.
$ cat /etc/udev/rules.d/60-palm.rules
# Palm handhelds — libusb access for pilot-link (pilot-xfer -p usb:)
SUBSYSTEM=="usb", ATTR{idVendor}=="0830", MODE="0660", GROUP="plugdev",
TAG+="uaccess"
With these permissions
$ ls -l /etc/udev/rules.d/60-palm.rules
-rw-r--r-- 1 root root 158 Aug 9 23:09 /etc/udev/rules.d/60-palm.rules
and then run "sudo udevadm control --reload-rules && sudo udevadm
trigger" to load it.
NOTICE that the usb rule specifies the group "plugdev", NOT dialout.
With this you'll need to be in the plugdev group, which seems to be more
modern than "dialout".
$ pilot-xfer -l -p usb:
Listening for incoming connection on usb:... connected!
Judd
On 8/11/26 16:14, Ulf Zibis wrote:
> This is not enough. I had to do:
> sudo apt install libpisync1=0.13.* libpisock9=0.13.* libpisock-dev=0.13.* pilot-link=0.13.* jpilot-plugins=2.0.2-1 jpilot=2.0.2-1
> sudo apt-mark hold libpisync1 libpisock9 libpisock-dev pilot-link jpilot-plugins jpilot
>
> Now JPilot syncs again with the long known crash at the end:
> [....]
> freeing plugin list
> Fertig.
> unlock succeeded
> command=100 [Fertig.
> ]
> sync child exiting
> command=105 [
> ]
> address_gui_cleanup()
> jp_pref_write_rc_file()
> jp_pref_write_rc_file()
> caught signal SIGCHLD
> Getötet
>
> It's a pity, that version 2.1.* is unusable.
>
> Hopefully you find the source of the problem.
>
> Thanks,
> Ulf
>
> Am 10.08.26 um 15:08 schrieb Judd Montgomery:
>> sudo apt install jpilot=2.0.2-1
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
UZ
Ulf Zibis
Tue, Aug 11, 2026 8:53 PM
"connected" was only with '/dev/ttyUSB1'
After "Listening for incoming connection on usb:..." there is "^C" which is Ctrl+C.
I had to cancel pilot-xfer, because there was NO connection within a minute.
Theese experiments were with version 0.15.*, module visor was unloaded.
-Ulf
Am 11.08.26 um 22:29 schrieb Judd Montgomery:
I think if you connected on /dev/ttyUSB1 then you have the visor module
loaded. Try rmmod visor.
I see a connection on usb:, not ttyUSB1.:
$ pilot-xfer -l -p usb:
Listening for incoming connection on usb:... connected!
...
Judd
On 8/10/26 09:17, Ulf Zibis wrote:
Ah, ok. I did:
$ sudo modprobe -r usbserial visor
modprobe: FATAL: Module usbserial is in use.
Now I can connect without visor, but only via -p /dev/ttyUSB1, not via usb, libusborusb:Is there another name or shortcut which can work? But I coudn't removeusbserial`.
===================
ich@W541:~$ pilot-xfer -p usb -l
Unable to bind to port: usb
Please use --help for more information
ich@W541:~$ pilot-xfer -p libusb -l
Unable to bind to port: libusb
Please use --help for more information
ich@W541:~$ pilot-xfer -p usb: -l
Listening for incoming connection on usb:... ^C
ich@W541:~$ pilot-xfer -p /dev/ttyUSB1 -l
Listening for incoming connection on /dev/ttyUSB1... connected!
Reading list of databases in RAM...
AddressingLibRecent-HsCh
MyTreoCASData
ADD053enUSSData
[......]
-Ulf
Am 10.08.26 um 14:39 schrieb Judd Montgomery:
About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
On August 10, 2026 8:31:06 AM EDT, Ulf Zibis Ulf.Zibis@CoSoCo.de wrote:
Hi Judd,
thanks.
-
So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
-
But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
Regards,
-Ulf
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
"connected" was only with '/dev/ttyUSB1'
After "Listening for incoming connection on usb:..." there is "^C" which is Ctrl+C.
I had to cancel `pilot-xfer`, because there was NO connection within a minute.
Theese experiments were with version 0.15.*, module visor was unloaded.
-Ulf
Am 11.08.26 um 22:29 schrieb Judd Montgomery:
> I think if you connected on /dev/ttyUSB1 then you have the visor module
> loaded. Try rmmod visor.
>
> I see a connection on usb:, not ttyUSB1.:
> $ pilot-xfer -l -p usb:
>
> Listening for incoming connection on usb:... connected!
> ...
>
> Judd
>
> On 8/10/26 09:17, Ulf Zibis wrote:
>> Ah, ok. I did:
>> $ sudo modprobe -r usbserial visor
>> modprobe: FATAL: Module usbserial is in use.
>>
>> Now I can connect without `visor`, but only via `-p /dev/ttyUSB1`, not via `usb`, libusb` or `usb:`
>> Is there another name or shortcut which can work?
>> But I coudn't remove `usbserial`.
>>
>> ===================
>> ich@W541:~$ pilot-xfer -p usb -l
>> Unable to bind to port: usb
>> Please use --help for more information
>>
>> ich@W541:~$ pilot-xfer -p libusb -l
>> Unable to bind to port: libusb
>> Please use --help for more information
>>
>> ich@W541:~$ pilot-xfer -p usb: -l
>>
>> Listening for incoming connection on usb:... ^C
>> ich@W541:~$ pilot-xfer -p /dev/ttyUSB1 -l
>>
>> Listening for incoming connection on /dev/ttyUSB1... connected!
>>
>> Reading list of databases in RAM...
>> AddressingLibRecent-HsCh
>> MyTreoCASData
>> ADD053enUSSData
>> [......]
>> ====================
>>
>> -Ulf
>>
>> Am 10.08.26 um 14:39 schrieb Judd Montgomery:
>>> About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
>>>
>>> You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
>>>
>>> On August 10, 2026 8:31:06 AM EDT, Ulf Zibis <Ulf.Zibis@CoSoCo.de> wrote:
>>>
>>>> Hi Judd,
>>>>
>>>> thanks.
>>>>
>>>> 1. So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
>>>>
>>>> 2. But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
>>>>
>>>> Regards,
>>>>
>>>> -Ulf
>> _______________________________________________
>> Jpilot mailing list -- jpilot@lists.jpilot.org
>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
UZ
Ulf Zibis
Tue, Aug 11, 2026 10:26 PM
Hey wow.
Now pilot-xfer -l -p usb: works fine here on Ubuntu 24.04.
And it's the first time, it works in both orders of pilot-xfer -l -p usb: --> "Press HotSync button" and vice versa.
With 0.13.* it only worked vice versa and the program should have been started within 3...7 seconds, not less and not more.
I'm still wondering, why I never saw the "Hit HotSync button" message, even without option -q or --quiet.
I still have:
$ cat /etc/udev/rules.d/pilot.rules
BUS=="usb", SYSFS{product}=="Palm Handheld*|Handspring ", KERNEL=="ttyUSB", NAME="ttyUSB%n", SYMLINK="pilot", GROUP="usb", MODE="0666"
I think, this old one should be removed by sudo apt install ...
And the new rule should be part of the rules in the Debian package.
Also JPilot 2.1.0-1 now works the first time with usb:. A big thanks to you !!!
But after sudo udevadm control --reload-rules && sudo udevadm trigger I again had at the end:
freeing plugin list
Fertig.
unlock succeeded
sync child exiting
command=100 [Fertig.
]
command=105 [
]
address_gui_cleanup()
jp_pref_write_rc_file()
caught signal SIGCHLD
Getötet
Well this sometimes occurs, sometimes not. As result, the GUI is no more responsive and I have to hard kill it.
Often, after restart, the prefs are set to default. I use to set the number of backups to 10, so when I missed to check the prefs after restart, 8 of 10 backups were deleted. This is severe dataloss.
Maybe you could show more detailed info on that in debug mode, so we can find the source.
Regards
-Ulf
Am 11.08.26 um 22:33 schrieb Judd Montgomery:
Hi Ulf,
I hope we figure it out also. I can't reproduce it and I don't
understand what is wrong so I can't fix it. I thought you were syncing
fine with /dev/ttyUSB1.
On a stock XUbuntu 26.04 box I needed to add this file.
$ cat /etc/udev/rules.d/60-palm.rules
Palm handhelds — libusb access for pilot-link (pilot-xfer -p usb:)
SUBSYSTEM=="usb", ATTR{idVendor}=="0830", MODE="0660", GROUP="plugdev",
TAG+="uaccess"
With these permissions
$ ls -l /etc/udev/rules.d/60-palm.rules
-rw-r--r-- 1 root root 158 Aug 9 23:09 /etc/udev/rules.d/60-palm.rules
and then run "sudo udevadm control --reload-rules && sudo udevadm
trigger" to load it.
NOTICE that the usb rule specifies the group "plugdev", NOT dialout.
With this you'll need to be in the plugdev group, which seems to be more
modern than "dialout".
$ pilot-xfer -l -p usb:
Listening for incoming connection on usb:... connected!
Judd
On 8/11/26 16:14, Ulf Zibis wrote:
This is not enough. I had to do:
sudo apt install libpisync1=0.13.* libpisock9=0.13.* libpisock-dev=0.13.* pilot-link=0.13.* jpilot-plugins=2.0.2-1 jpilot=2.0.2-1
sudo apt-mark hold libpisync1 libpisock9 libpisock-dev pilot-link jpilot-plugins jpilot
Now JPilot syncs again with the long known crash at the end:
[....]
freeing plugin list
Fertig.
unlock succeeded
command=100 [Fertig.
]
sync child exiting
command=105 [
]
address_gui_cleanup()
jp_pref_write_rc_file()
jp_pref_write_rc_file()
caught signal SIGCHLD
Getötet
It's a pity, that version 2.1.* is unusable.
Hopefully you find the source of the problem.
Thanks,
Ulf
Am 10.08.26 um 15:08 schrieb Judd Montgomery:
sudo apt install jpilot=2.0.2-1
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Hey wow.
Now `pilot-xfer -l -p usb:` works fine here on Ubuntu 24.04.
And it's the first time, it works in both orders of `pilot-xfer -l -p usb:` --> "Press HotSync button" and vice versa.
With 0.13.* it only worked vice versa and the program should have been started within 3...7 seconds, not less and not more.
I'm still wondering, why I never saw the "Hit HotSync button" message, even without option `-q` or `--quiet`.
I still have:
$ cat /etc/udev/rules.d/pilot.rules
BUS=="usb", SYSFS{product}=="Palm Handheld*|Handspring *", KERNEL=="ttyUSB*", NAME="ttyUSB%n", SYMLINK="pilot", GROUP="usb", MODE="0666"
I think, this old one should be removed by `sudo apt install ...`
And the new rule should be part of the rules in the Debian package.
Also JPilot 2.1.0-1 now works the first time with `usb:`. A big thanks to you !!!
But after `sudo udevadm control --reload-rules && sudo udevadm trigger` I again had at the end:
freeing plugin list
Fertig.
unlock succeeded
sync child exiting
command=100 [Fertig.
]
command=105 [
]
address_gui_cleanup()
jp_pref_write_rc_file()
caught signal SIGCHLD
Getötet
Well this sometimes occurs, sometimes not. As result, the GUI is no more responsive and I have to hard kill it.
Often, after restart, the prefs are set to default. I use to set the number of backups to 10, so when I missed to check the prefs after restart, 8 of 10 backups were deleted. This is severe dataloss.
Maybe you could show more detailed info on that in debug mode, so we can find the source.
Regards
-Ulf
Am 11.08.26 um 22:33 schrieb Judd Montgomery:
> Hi Ulf,
>
> I hope we figure it out also. I can't reproduce it and I don't
> understand what is wrong so I can't fix it. I thought you were syncing
> fine with /dev/ttyUSB1.
>
> On a stock XUbuntu 26.04 box I needed to add this file.
>
> $ cat /etc/udev/rules.d/60-palm.rules
> # Palm handhelds — libusb access for pilot-link (pilot-xfer -p usb:)
> SUBSYSTEM=="usb", ATTR{idVendor}=="0830", MODE="0660", GROUP="plugdev",
> TAG+="uaccess"
>
> With these permissions
> $ ls -l /etc/udev/rules.d/60-palm.rules
> -rw-r--r-- 1 root root 158 Aug 9 23:09 /etc/udev/rules.d/60-palm.rules
>
> and then run "sudo udevadm control --reload-rules && sudo udevadm
> trigger" to load it.
>
> NOTICE that the usb rule specifies the group "plugdev", NOT dialout.
> With this you'll need to be in the plugdev group, which seems to be more
> modern than "dialout".
>
> $ pilot-xfer -l -p usb:
>
> Listening for incoming connection on usb:... connected!
>
> Judd
>
> On 8/11/26 16:14, Ulf Zibis wrote:
>> This is not enough. I had to do:
>> sudo apt install libpisync1=0.13.* libpisock9=0.13.* libpisock-dev=0.13.* pilot-link=0.13.* jpilot-plugins=2.0.2-1 jpilot=2.0.2-1
>> sudo apt-mark hold libpisync1 libpisock9 libpisock-dev pilot-link jpilot-plugins jpilot
>>
>> Now JPilot syncs again with the long known crash at the end:
>> [....]
>> freeing plugin list
>> Fertig.
>> unlock succeeded
>> command=100 [Fertig.
>> ]
>> sync child exiting
>> command=105 [
>> ]
>> address_gui_cleanup()
>> jp_pref_write_rc_file()
>> jp_pref_write_rc_file()
>> caught signal SIGCHLD
>> Getötet
>>
>> It's a pity, that version 2.1.* is unusable.
>>
>> Hopefully you find the source of the problem.
>>
>> Thanks,
>> Ulf
>>
>> Am 10.08.26 um 15:08 schrieb Judd Montgomery:
>>> sudo apt install jpilot=2.0.2-1
>> _______________________________________________
>> Jpilot mailing list -- jpilot@lists.jpilot.org
>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
UZ
Ulf Zibis
Tue, Aug 11, 2026 10:39 PM
So please set the default at least to 5 backups.
Also please remove the default of "Show alarm reminder." If it is set, after sync all reminder messages on the real device are gone.
-Ulf
Am 12.08.26 um 00:26 schrieb Ulf Zibis:
Often, after restart, the prefs are set to default. I use to set the number of backups to 10, so when I missed to check the prefs after restart, 8 of 10 backups were deleted. This is severe dataloss.
So please set the default at least to 5 backups.
Also please remove the default of "Show alarm reminder." If it is set, after sync all reminder messages on the real device are gone.
-Ulf
Am 12.08.26 um 00:26 schrieb Ulf Zibis:
> Often, after restart, the prefs are set to default. I use to set the number of backups to 10, so when I missed to check the prefs after restart, 8 of 10 backups were deleted. This is severe dataloss.
JM
Judd Montgomery
Wed, Aug 12, 2026 12:29 AM
This is good progress! I am sending you an off-list email to try to fix
this.
Judd
On 8/11/26 18:26, Ulf Zibis wrote:
Hey wow.
Now pilot-xfer -l -p usb: works fine here on Ubuntu 24.04.
And it's the first time, it works in both orders of pilot-xfer -l -p usb: --> "Press HotSync button" and vice versa.
With 0.13.* it only worked vice versa and the program should have been started within 3...7 seconds, not less and not more.
I'm still wondering, why I never saw the "Hit HotSync button" message, even without option -q or --quiet.
I still have:
$ cat /etc/udev/rules.d/pilot.rules
BUS=="usb", SYSFS{product}=="Palm Handheld*|Handspring ", KERNEL=="ttyUSB", NAME="ttyUSB%n", SYMLINK="pilot", GROUP="usb", MODE="0666"
I think, this old one should be removed by sudo apt install ...
And the new rule should be part of the rules in the Debian package.
Also JPilot 2.1.0-1 now works the first time with usb:. A big thanks to you !!!
But after sudo udevadm control --reload-rules && sudo udevadm trigger I again had at the end:
freeing plugin list
Fertig.
unlock succeeded
sync child exiting
command=100 [Fertig.
]
command=105 [
]
address_gui_cleanup()
jp_pref_write_rc_file()
caught signal SIGCHLD
Getötet
Well this sometimes occurs, sometimes not. As result, the GUI is no more responsive and I have to hard kill it.
Often, after restart, the prefs are set to default. I use to set the number of backups to 10, so when I missed to check the prefs after restart, 8 of 10 backups were deleted. This is severe dataloss.
Maybe you could show more detailed info on that in debug mode, so we can find the source.
Regards
-Ulf
Am 11.08.26 um 22:33 schrieb Judd Montgomery:
Hi Ulf,
I hope we figure it out also. I can't reproduce it and I don't
understand what is wrong so I can't fix it. I thought you were syncing
fine with /dev/ttyUSB1.
On a stock XUbuntu 26.04 box I needed to add this file.
$ cat /etc/udev/rules.d/60-palm.rules
Palm handhelds — libusb access for pilot-link (pilot-xfer -p usb:)
SUBSYSTEM=="usb", ATTR{idVendor}=="0830", MODE="0660", GROUP="plugdev",
TAG+="uaccess"
With these permissions
$ ls -l /etc/udev/rules.d/60-palm.rules
-rw-r--r-- 1 root root 158 Aug 9 23:09 /etc/udev/rules.d/60-palm.rules
and then run "sudo udevadm control --reload-rules && sudo udevadm
trigger" to load it.
NOTICE that the usb rule specifies the group "plugdev", NOT dialout.
With this you'll need to be in the plugdev group, which seems to be more
modern than "dialout".
$ pilot-xfer -l -p usb:
Listening for incoming connection on usb:... connected!
Judd
On 8/11/26 16:14, Ulf Zibis wrote:
This is not enough. I had to do:
sudo apt install libpisync1=0.13.* libpisock9=0.13.* libpisock-dev=0.13.* pilot-link=0.13.* jpilot-plugins=2.0.2-1 jpilot=2.0.2-1
sudo apt-mark hold libpisync1 libpisock9 libpisock-dev pilot-link jpilot-plugins jpilot
Now JPilot syncs again with the long known crash at the end:
[....]
freeing plugin list
Fertig.
unlock succeeded
command=100 [Fertig.
]
sync child exiting
command=105 [
]
address_gui_cleanup()
jp_pref_write_rc_file()
jp_pref_write_rc_file()
caught signal SIGCHLD
Getötet
It's a pity, that version 2.1.* is unusable.
Hopefully you find the source of the problem.
Thanks,
Ulf
Am 10.08.26 um 15:08 schrieb Judd Montgomery:
sudo apt install jpilot=2.0.2-1
This is good progress! I am sending you an off-list email to try to fix
this.
Judd
On 8/11/26 18:26, Ulf Zibis wrote:
> Hey wow.
>
> Now `pilot-xfer -l -p usb:` works fine here on Ubuntu 24.04.
>
> And it's the first time, it works in both orders of `pilot-xfer -l -p usb:` --> "Press HotSync button" and vice versa.
> With 0.13.* it only worked vice versa and the program should have been started within 3...7 seconds, not less and not more.
> I'm still wondering, why I never saw the "Hit HotSync button" message, even without option `-q` or `--quiet`.
>
> I still have:
> $ cat /etc/udev/rules.d/pilot.rules
> BUS=="usb", SYSFS{product}=="Palm Handheld*|Handspring *", KERNEL=="ttyUSB*", NAME="ttyUSB%n", SYMLINK="pilot", GROUP="usb", MODE="0666"
> I think, this old one should be removed by `sudo apt install ...`
>
> And the new rule should be part of the rules in the Debian package.
>
> Also JPilot 2.1.0-1 now works the first time with `usb:`. A big thanks to you !!!
>
> But after `sudo udevadm control --reload-rules && sudo udevadm trigger` I again had at the end:
> freeing plugin list
> Fertig.
> unlock succeeded
> sync child exiting
> command=100 [Fertig.
> ]
> command=105 [
> ]
> address_gui_cleanup()
> jp_pref_write_rc_file()
> caught signal SIGCHLD
> Getötet
>
> Well this sometimes occurs, sometimes not. As result, the GUI is no more responsive and I have to hard kill it.
> Often, after restart, the prefs are set to default. I use to set the number of backups to 10, so when I missed to check the prefs after restart, 8 of 10 backups were deleted. This is severe dataloss.
> Maybe you could show more detailed info on that in debug mode, so we can find the source.
>
> Regards
> -Ulf
>
>
> Am 11.08.26 um 22:33 schrieb Judd Montgomery:
>> Hi Ulf,
>>
>> I hope we figure it out also. I can't reproduce it and I don't
>> understand what is wrong so I can't fix it. I thought you were syncing
>> fine with /dev/ttyUSB1.
>>
>> On a stock XUbuntu 26.04 box I needed to add this file.
>>
>> $ cat /etc/udev/rules.d/60-palm.rules
>> # Palm handhelds — libusb access for pilot-link (pilot-xfer -p usb:)
>> SUBSYSTEM=="usb", ATTR{idVendor}=="0830", MODE="0660", GROUP="plugdev",
>> TAG+="uaccess"
>>
>> With these permissions
>> $ ls -l /etc/udev/rules.d/60-palm.rules
>> -rw-r--r-- 1 root root 158 Aug 9 23:09 /etc/udev/rules.d/60-palm.rules
>>
>> and then run "sudo udevadm control --reload-rules && sudo udevadm
>> trigger" to load it.
>>
>> NOTICE that the usb rule specifies the group "plugdev", NOT dialout.
>> With this you'll need to be in the plugdev group, which seems to be more
>> modern than "dialout".
>>
>> $ pilot-xfer -l -p usb:
>>
>> Listening for incoming connection on usb:... connected!
>>
>> Judd
>>
>> On 8/11/26 16:14, Ulf Zibis wrote:
>>> This is not enough. I had to do:
>>> sudo apt install libpisync1=0.13.* libpisock9=0.13.* libpisock-dev=0.13.* pilot-link=0.13.* jpilot-plugins=2.0.2-1 jpilot=2.0.2-1
>>> sudo apt-mark hold libpisync1 libpisock9 libpisock-dev pilot-link jpilot-plugins jpilot
>>>
>>> Now JPilot syncs again with the long known crash at the end:
>>> [....]
>>> freeing plugin list
>>> Fertig.
>>> unlock succeeded
>>> command=100 [Fertig.
>>> ]
>>> sync child exiting
>>> command=105 [
>>> ]
>>> address_gui_cleanup()
>>> jp_pref_write_rc_file()
>>> jp_pref_write_rc_file()
>>> caught signal SIGCHLD
>>> Getötet
>>>
>>> It's a pity, that version 2.1.* is unusable.
>>>
>>> Hopefully you find the source of the problem.
>>>
>>> Thanks,
>>> Ulf
>>>
>>> Am 10.08.26 um 15:08 schrieb Judd Montgomery:
>>>> sudo apt install jpilot=2.0.2-1
>>> _______________________________________________
>>> Jpilot mailing list -- jpilot@lists.jpilot.org
>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
>> _______________________________________________
>> Jpilot mailing list -- jpilot@lists.jpilot.org
>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
UZ
Ulf Zibis
Thu, Aug 13, 2026 9:52 AM
2 additional sugesstions to deal with that problems:
-
When rebuilding the default prefs, use max(4, number_of_already_existing_backups).
-
Add a checkbox to the reminder dialogue: "Also cancel this reminder on the device on next HotSync" and default it to unchecked.
-Ulf
Am 12.08.26 um 00:39 schrieb Ulf Zibis:
So please set the default at least to 5 backups.
Also please remove the default of "Show alarm reminder." If it is set, after sync all reminder messages on the real device are gone.
-Ulf
Am 12.08.26 um 00:26 schrieb Ulf Zibis:
Often, after restart, the prefs are set to default. I use to set the number of backups to 10, so when I missed to check the prefs after restart, 8 of 10 backups were deleted. This is severe dataloss.
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
2 additional sugesstions to deal with that problems:
1. When rebuilding the default prefs, use `max(4, number_of_already_existing_backups)`.
2. Add a checkbox to the reminder dialogue: "Also cancel this reminder on the device on next HotSync" and default it to unchecked.
-Ulf
Am 12.08.26 um 00:39 schrieb Ulf Zibis:
> So please set the default at least to 5 backups.
>
> Also please remove the default of "Show alarm reminder." If it is set, after sync all reminder messages on the real device are gone.
>
> -Ulf
>
> Am 12.08.26 um 00:26 schrieb Ulf Zibis:
>> Often, after restart, the prefs are set to default. I use to set the number of backups to 10, so when I missed to check the prefs after restart, 8 of 10 backups were deleted. This is severe dataloss.
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
