That indeed seems to be the problem. Thinking back I've used lsusb to check the id's..
I'll see if I can add this to the bug report. Qball On Sun, 2006-03-05 at 14:21 +0000, Matt Davey wrote: > Oh, just remembered another possible problem: gnome-pilot > requires the file /proc/bus/usb/devices to exist, and will silently > ignore USB palms if it can't read that file. > > Can some ubuntu dapper user confirm whether that file exists? > > Matt > > > > It seems to be a known dapper problem. On the forum more people complain > > > about it. (I have the same problem). > > > The palm will sync fine with jpilot, and also do some kind of sync with > > > multisync. Yet gpilot is completely unresponsive. > > > > The original poster said the pilot-xfer / install-user didn't work > > for him. This suggests no connectivity to the palm, which makes > > it seem unlikely that it is the same problem you describe, as I > > would doubt that jpilot could work if pilot-link tools don't. > > > > I'd be interested to know what 'known dapper problem' you're referring > > to. Can you post links to the forum messages? > > > > Usually, when gnome-pilot isn't working and other tools are, it's > > just a case of adding the correct USB IDs into the devices.xml file. > > I'm not saying that's the case here, just that until you get pilot-link > > working there's no reason to assume you've got a gnome-pilot problem. > _______________________________________________ > gnome-pilot-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gnome-pilot-list _______________________________________________ gnome-pilot-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
