Re: Problem synching Handspring Treo 180g over USB

[Thomas Maeder <maeder+gnome-pilot-list glue ch>]

Am Mon, 2003-07-07 um 12.01 schrieb David A. Desrosiers: 
> --BEGIN PGP SIGNED MESSAGE--
> Hash: SHA1
> 
> 
> > > 	Does pilot-link work with this device, with gpilotd killed off?
> 
> > No. A gpilotd process is a necessary, but not sufficient (as
> > gnome-control-center has to be open) requirement.
> 
> 	Definately sounds like a weird misconfiguration, because
> gnome-control-center in no way is hooked to gpilotd.

So what is supposed to start gpilotd?


> If you close
> gnome-control-center (not gnomecc, I assume, that's the old control center),
> gpilotd dies?

No. This doesn't mean that I'm able to sync, though.

And no, gnomecc is no longer on my box:

% rpm -q gnomecc
Paket gnomecc ist nicht installiert


>  I'd try running it from a terminal and see what happens.
> gpilotd shouldn't be getting killed off by gnome-control-center, and if it
> is, then there is definatey something amiss here.

It's not getting killed. But there is definatey something amiss here
anyway.

> 	Launch gpilotd in one terminal, and gnome-control-center in another.
> Configure gnome-pilot via control center, then exit control center. What
> happens to the gpilotd in the other terminal? What errors do you see?

1. I start gpilotd in one terminal:

% /opt/gnome2/libexec/gpilotd
gpilotd-Message: gnome-pilot 2.0.9 starting...
gpilotd-Message: compiled for pilot-link version 0.11.7
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Cradle (/dev/pilot) wird betrachtet

[the last line means: observing cradle (/dev/pilot)]


2. I start gnome-control-center in another terminal;

% gnome-control-center
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0


3. I open the Pilot applet and change some setting, only to revert it
back, then close the applet:

** Message: Pilot name -> MyPilot
** Message: Pilot id   -> 13547
** Message: Pilot username -> Thomas Maeder
** Message: Pilot creation/rom = 0/0
** Message: Cradle Type -> USB
** Message: cradle device name -> Cradle
** Message: cradle device name -> /dev/pilot
** Message: Pilot Speed  -> 57600
** Message: Timeout -> 2
gpilotd-Message: Activating object OAFIID:GNOME_Pilot_Daemon
** Message: pilot = MyPilot
** Message: Pilot name -> MyPilot
** Message: Pilot id   -> 13547
** Message: Pilot username -> Thomas Maeder
** Message: Pilot creation/rom = 0/0
** Message: Cradle Type -> USB
** Message: cradle device name -> Cradle
** Message: cradle device name -> /dev/pilot
** Message: Pilot Speed  -> 57600
** Message: Timeout -> 2

, which causes gpilotd to produce this in its terminal:

gpilotd-Message: Client seems ok
gpilotd-Message: Client seems ok
gpilotd-Message: monitor_on(pilot_name="MyPilot",client_id =
IOR:01e9ffbf1b000000...)
gpilotd-Message: corba:
notify_on(event_type=CONNECT,callback=IOR:01e9ffbf1b000000...)
gpilotd-Message: corba:
notify_on(event_type=DISCONNECT,callback=IOR:01e9ffbf1b000000...)
gpilotd-Message: Geräte werden heruntergefahren
gpilotd-Message: Konfiguration neu einlesen...
gpilotd-Message: Cradle (/dev/pilot) wird betrachtet

[the last 3 lines mean:
Shutting down devices
Reading configuration ...
Observing cradle (/dev/pilot)]


> 	This is the first time I've ever heard of something like this.

Let me ask (again):
- what processes need to be running for the sync to start?
- what is starting these processes?
- where is all this configured?
- what RPMs have to be installed minimally?
- what things have to be done other than intalling these RPMs for things
to work?
- where do I find documentation about all this?