I had done similar to what you suggested, re: multiple terminal
windows. Here is what I recorded for your reference:
gpilotd terminal window...
[dcvet Terminator dcvet]$ /usr/libexec/gpilotd
--oaf-activ
gpilotd-Message: gnome-pilot 2.0.9 starting...
gpilotd-Message: compiled for pilot-link version 0.11.5
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)
** at this point, I would invoke the gnome-control-center in another
terminal
** and the following messages appear
gpilotd-Message: Client seems ok
gpilotd-Message: Client seems ok
gpilotd-Message: monitor_on(pilot_name="MyPilot",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...)
** the above are new messages generated when I started up the
** gnome-control-center in the other terminal
gpilotd-Message: Shutting down devices
gpilotd-Message: Rereading configuration...
gpilotd-Message: Watching Cradle (/dev/pilot)
** the above messages were generated after disabling the memo
** conduit
gpilotd-Message: Shutting down devices
gpilotd-Message: Rereading configuration...
gpilotd-Message: Watching Cradle (/dev/pilot)
gpilotd-Message: Shutting down devices
gpilotd-Message: Rereading configuration...
gpilotd-Message: Watching Cradle (/dev/pilot)
** the above messages were generated after re-enabling the memo
** conduit - don't know why it's repeated, but it is
...
gnome-control-center terminal window...
[dcvet Terminator dcvet]$ gnome-control-center
** Message: Pilot name -> MyPilot
** Message: Pilot id -> 22359
** Message: Pilot username -> David M. Cvet
** 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 -> 45
gpilotd-Message: Activating object OAFIID:GNOME_Pilot_Daemon
** Message: pilot = MyPilot
** Message: Pilot name -> MyPilot
** Message: Pilot id -> 22359
** Message: Pilot username -> David M. Cvet
** 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 -> 45
** the above messages were generated after the gnome-control-center
** was started which generated the messages indicated above in the
** other terminal
** note, disabling the memo conduit did not generate any messages
** from the gnome-control-center
memo-file-conduit-Message: creating memo_file conduit
memo-file-conduit-Message: create_settings_window
memo-file-conduit-Message: save_settings
** the above messages generated after enabling the memo conduit
** Note: memo conduit never worked, but its behaviour in terms of
** enabling/disabling is the same as the other conduits that did work
** before the patches were applied
[dcvet Terminator dcvet]$
** once the settings window was closed, I came back to the command
prompt
Does this help in determining the problem? The inability to sync while
the above were active did nothing to generate any error messages.
/dc
David A. Desrosiers wrote:
-----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. If you close
gnome-control-center (not gnomecc, I assume, that's the old control center),
gpilotd dies? 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.
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?
This is the first time I've ever heard of something like this.
d.
perldoc -qa.j | perl -lpe '($_)=m("(.*)")'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/CUUIkRQERnB1rkoRArJsAJ9u57q0y0+TfyAHsy4ygxkM05QcNQCeI4DD
da7ZJY4lUpP5uqHcy3K58V0=
=jJoY
-----END PGP SIGNATURE-----
_______________________________________________
gnome-pilot-list mailing list
gnome-pilot-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
--
____________________________________________________________
David M. Cvet
401-159 Frederick St., Toronto, Ont. Canada M5A 4P1
CELL:+1 416 726-8314 FAX:+1 416 366-7448
____________________________________________________________
|
