Joel: > 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?
You should be able to set it to 'usb:' using the config applet. It should even be one of the options in the drop down list. > One thing I did notice is that when gpilotd is run at the command line > is says: [...] > (gnome-pilot:21866): gpilotd-WARNING **: Number of devices is configured to 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? Have you edited your ~/.gnome2/gnome-pilot.d/gpilot? Is it possible that it's been mucked up so that gpilotd can't parse it? I can't think of a good reason to edit that file by hand, at least with pilot-link 0.12 and gp 2.0.14. You could try removing or moving your ~/.gnome2/gnome-pilot.d directory altogether and trying the config steps again. Matt -- After one sync, connections to a Tungsten T3 device fails https://launchpad.net/bugs/67077 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs