Not really. While "If I load the pilot-link and jpilot packages and modprobe visor and use ttyUSB1 then I can sync to jpilot" - but I don't want to use the jpilot PIM. Gnome-pilot sees the PDA and the sync acts like it is going to work (the Clie makes the sync sound) but gnome-pilot then immediately fails and pops up a dialog box that reads "Device error on cradle (/dev/pilot) Caught unhandled port error".
Anyway, even if I could sync to ttyUSB1, I really would like to understand why "sub:" will not work i it should!
If I can solve this I plan on putting my Windows box to sleep (RIP). Being able to use my Pal Pilot is a MUST (it is my substitute brain) for making the final switch to 100% Linux after years of waiting for the Linux desktop to get to a level of usability that suited my needs. Ubuntu is "so close" but things like this bug are stopping it from reaching the finish line for me. I really want to switch!
Not really. While "If I load the pilot-link and jpilot packages and modprobe visor and use ttyUSB1 then I can sync to jpilot" - but I don't want to use the jpilot PIM. Gnome-pilot sees the PDA and the sync acts like it is going to work (the Clie makes the sync sound) but gnome-pilot then immediately fails and pops up a dialog box that reads "Device error on cradle (/dev/pilot) Caught unhandled port error".
Anyway, even if I could sync to ttyUSB1, I really would like to understand why "sub:" will not work i it should!
If I can solve this I plan on putting my Windows box to sleep (RIP). Being able to use my Pal Pilot is a MUST (it is my substitute brain) for making the final switch to 100% Linux after years of waiting for the Linux desktop to get to a level of usability that suited my needs. Ubuntu is "so close" but things like this bug are stopping it from reaching the finish line for me. I really want to switch!