Re: I can't sync my TE2

[Qball Cow <qball qballcow nl>]

On Sun, 2006-03-05 at 14:08 +0000, Matt Davey wrote:
> > 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'm sorry, dropped in 1/2 way the conversation.
> I'd be interested to know what 'known dapper problem' you're referring
> to.  Can you post links to the forum messages?

f.e. in the bug tracker:
https://launchpad.net/distros/ubuntu/+source/gnome-pilot/+bug/33285
https://launchpad.net/distros/ubuntu/+source/gnome-pilot/+bug/25653
This fix doesnt work for me, my device id's are available in de
device.xml:
https://bugzilla.ubuntu.com/show_bug.cgi?id=3329

forum posts (one of multiple):
http://ubuntuforums.org/showthread.php?t=128603&highlight=gpilot


> 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.

I've check those, in my case it's there. (see above)

I've just saw the last messages, and I thought it looked very similar to
this.

Sorry for barging in,

Qball