Hi Matt, Indeed I only have one gpilotd. I attempted to get libusb working. - that seems fine as i got pilot-xfer -p usb: -l to work. But I did have a question about ~/.gnome2/gnome-pilot.d/gpilot I could not figure out what to set /dev/pilot to? I tried device=/dev/bus/usb/002/001 which is the actual Palm usb device, and that didn't work. Any ideas?
One thing I did notice is that when gpilotd is run at the command line is says: gpilotd-Message: gnome-pilot 2.0.14 starting... gpilotd-Message: compiled for pilot-link version 0.12.1 gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network] (gnome-pilot:21866): gpilotd-WARNING **: Number of devices is configured to 0 (gnome-pilot:21866): gpilotd-WARNING **: No accessible devices available (gnome-pilot:21866): gpilotd-WARNING **: Number of PDAs is configured to 0 gpilotd-Message: Activating CORBA server gpilotd-Message: bonobo_activation_active_server_register = 0 Which seems to imply that it doesn't read the same config as when the applet runs gpilotd. Could that be the problem since sync works after this if I run the applet and then sync? Thanks, Joel -- After one sync, connections to a Tungsten T3 device fails https://launchpad.net/bugs/67077 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
