Re: can't sync with Tungsten T2

I found Bug #66355 "gpilotd locks up my Palm Z22" and (after installing
pilot-xfer) have tried

daz@daz-laptop:~$ pilot-xfer -p /dev/pilot -l

   Listening for incoming connection on /dev/pilot... 

But nothing happens.....
I don't think that its the cable, as the charging light is on,
and /dev/pilot is definitely created when I hit the hotsync button.

Darren


On Sun, 2007-08-19 at 09:02 +1000, daz wrote:
> I removed the applet, ran a killall gpilotd, started gpilotd manually,
> then hit the hotsync button:
> 
> daz@daz-laptop:~$ /usr/bin/gpilotd
> gpilotd-Message: gnome-pilot 2.0.15 starting...
> gpilotd-Message: compiled for pilot-link version 0.12.1
> gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network] 
> gpilotd-Message: Activating CORBA server
> gpilotd-Message: bonobo_activation_active_server_register = 0
> gpilotd-Message: Watching Cradle (/dev/pilot)
> gpilotd-Message: Found 4766, 0001
> gpilotd-Message: Using net TRUE
> gpilotd-Message: Found 0502, 0736
> gpilotd-Message: Using net TRUE
> gpilotd-Message: Found 091e, 0004
> gpilotd-Message: Using net TRUE
> 
> ........lots of these then,
> 
> gpilotd-Message: Using net TRUE
> gpilotd-Message: Found 12ef, 0100
> gpilotd-Message: Using net TRUE
> gpilotd-Message: setting PILOTRATE=57600
> 
> (gnome-pilot:29864): gpilotd-WARNING **: pi_accept_to returned -202:
> Resource temporarily unavailable
> 
> (gnome-pilot:29864): gpilotd-WARNING **: pi_accept_to: timeout was 2
> secs
> 
> Then I disconnected the PDA:
> 
> gpilotd-Message: Client seems ok
> gpilotd-Message: Client seems ok
> gpilotd-Message: monitor_on(pilot_name="PalmT5",client_id =
> IOR:010000001b000000...)
> gpilotd-Message: corba:
> notify_on(event_type=CONNECT,callback=IOR:010000001b000000...)
> gpilotd-Message: corba:
> notify_on(event_type=DISCONNECT,callback=IOR:010000001b000000...)
> gpilotd-Message: Shutting down devices
> gpilotd-Message: Rereading configuration...
> gpilotd-Message: Watching Cradle (/dev/pilot)
> 
> Now I disable all the conduits and hit the hotsync button:
> 
> gpilotd-Message: setting PILOTRATE=57600
> 
> (gnome-pilot:29864): gpilotd-WARNING **: pi_accept_to returned -202:
> Resource temporarily unavailable
> 
> (gnome-pilot:29864): gpilotd-WARNING **: pi_accept_to: timeout was 2
> secs
> 
> Now its frozen again and I'm not getting the same stuff as above when I
> disconnect the PDA (dunno what happened there...).
> 
> 
> 
> 
> 
> On Sat, 2007-08-18 at 18:34 +0100, Matt Davey wrote:
> > > I've just recently installed Ubuntu 7.04 from a downloaded CD image.
> > > I'm running on an IBM A31 laptop.
> > > Gnome-Pilot-Applet is 2.0.15
> > > 
> > > I've been unable to sync my Palm Tungsten T2 via the USB port. It just
> > > freezes completely and requires a soft reset to come back to life (even
> > > the light that indicates that its charging stays on!).
> > 
> > Have you downloaded all available updates for your Ubuntu installation?
> > There are several bugs this could be, including:
> > https://launchpad.net/ubuntu/+source/gnome-pilot/+bug/19528
> > 
> > As suggested, you can run gpilotd in a terminal to get more
> > information about where it crashes.  My guess is that it is
> > crashing in the Evolution calendar conduit.  If you're not
> > sure, try disabling all the conduits and see if you can sync.
> > If that works, try re-enabling them one at a time to narrow
> > it down.
> > 
> > Matt
> > _______________________________________________
> > 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
>