On Thu, 2005-11-10 at 02:17 -0700, Veerapuram Varadhan wrote:
> Hi Andrew,
> 
> On Wed, 2005-11-09 at 20:54 +0000, Andrew Greig  wrote:
> 
> [snip]
> > > 2) Run "gpilotd" from a terminal.  This way you can see debug
> messages
> > > on the screen.
> > 
> > I typed gpilotd<TAB> here is the output
> > [EMAIL PROTECTED] ~]$ gpilotd
> > gpilotd-control-applet   gpilotd-session-wrapper
> > 
> > There is no plain "gpilotd" to run so I went with
> gpilotd-control-applet
> > 
> gpilotd is normally not installed in any of the "bin" directories.  You
> can find it either in "<gnome-prefix>/lib/gnome-pilot/" or
> "<gnome-prefix>/libexec/" or just a locate will find it for you.
> 
> [snip]
> > I checked the ownership attributes of my address data file in
> .evolution
> > and it was set to andrew:andrew which should be fine as my user and
> > group number are 501.  But should I change it to 501:501 ?
> 
> You don't have to actually change the ownership etc.  
> 
> As per your first mail, you have mentioned that you are using /dev/pilot
> as your pilot device and that it points to /dev/ttyS0. 
> 
> The device node actually gets created at the time of hotsync.  So, I am
> not sure whether hardcoding ownerships etc will help.
> 
> Does pilot-xfer command works for you on /dev/pilot?
> 
> Also, run "gpilotd" from shell and mail us with the "screen dump".
> 
> HTH,
> 
> V. Varadhan 


Hi Veerapuram,

I found it as you said.  I ran ps -aux first to find the running process
and then killed it.  So here is the screen dump, hope this helps.  I
have configured the pilot to access /dev/ttyS0 instead of /dev/pilot,
you can see that it connects but then no transfer takes place.  I had
set up the conduit for a one time only, Copy to Pilot.

[EMAIL PROTECTED] ~]$ /usr/lib/gpilotd
gpilotd-Message: gnome-pilot 2.0.13 starting...
gpilotd-Message: compiled for pilot-link version 0.11.8
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/ttyS0)
gpilotd-Message: Woke on Cradle
gpilotd-Message: setting PILOTRATE=57600
gpilotd-Message: Cradle Cradle has 0 events
gpilotd-Message: Instantiating 1 conduits...
eaddrconduit-Message: in address's conduit_get_gpilot_conduit

gpilotd-Message: Instantiated 0 backup conduits, 0 file conduits, 1
other conduits
gpilotd-Message: HotSync button pressed, synchronizing pilot
gpilotd-Message: Pilot ID is 501, name is MyPilot, owner is Andrew Greig
gpilotd-Message: Pilot has 0 entries in restore queue
gpilotd-Message: Pilot has 0 entries in conduit queue
gpilotd-Message: Conduit EAddress's first synchronization...
eaddrconduit-Message:
---------------------------------------------------------

eaddrconduit-Message: pre_sync: Addressbook Conduit v.0.1.2

(gpilotd:20561): eaddrconduit-WARNING **: Could not read pilot's Address
application block

(gpilotd:20561): eaddrconduit-WARNING **: dlp_ReadAppBlock(...) = -1

(gpilotd:20561): gpilotd-WARNING **: Copy to pilot failed!

(gpilotd:20561): gpilotd-WARNING **: Unable to open conduit!
gpilotd-Message: Synchronization ended



Many thanks
Andrew Greig

_______________________________________________
Evolution-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/evolution-list

Reply via email to