Re: Cannot get Pilot to sync at all

[Dan Hensley <dan hensley att net>]

Eskil Heyn Olsen wrote:

> On Wed, 12 Jan 2000, Dan Hensley wrote:
>
> > gpilotd-CRITICAL **: file lib-gpilotd.c: line 463 (gpilotd_get_user_info):
> > assertion `cradle!=NULL' failed.
> > Message: cancelling -1
>
> This is case of the pilot-link capplet lacking error handling. The
> intermediate libgpilotd fails the request, as the cradle name == NULL, but
> the capplet does not react to error state that is returned (everybody slap
> eskil!).
>
> As to why it is called with NULL, is actually a bit odd, it seems that it
> has written the correct info. Is the problem still occuring in the 0.1.48
> (there was a paradigm shift in cradle naming somewhere between .46 and
> .47)

I just tried it again with 0.1.48 (I had been using the pre-announce 0.1.48
when I wrote the original email).  It still didn't work.  This time I left the
gnome-pilot.d directory intact before starting gnomecc.  I verified that
gpilotd was not running.  Then I clicked on Pilot Link, and nothing showed up
in gnomecc, but this appeared in the terminal:

Gdk-WARNING **: locale not supported by C library

Gdk-WARNING **: locale not supported by C library
Message: Pilot name -> MyPilot
Message: Pilot id   -> 501
Message: Pilot username -> Dan Hensley
Message: Pilot sync_action -> custom
Message: cradle device port -> /dev/ttyS0
Message: cradle device name -> Cradle0
Message: Pilot Speed  -> 57600

I hit the Hotsync button on the cradle, but still nothing.  So I hit Cancel,
then Pilot Link again.  I got a repeat of the above message, but still
nothing.  Then a few seconds later gnomecc crashed.  I checked, and I had two
instances of gpilotd running.

This last message appeared, but I can't remember if it happened before I hit
Cancel or after.

Gtk-CRITICAL **: file gtksignal.c: line 593 (gtk_signal_emit_by_name):
assertion `object != NULL' failed.

This shouldn't matter, but I have to share my serial port with my external
modem.  This go-around I didn't try starting gpilotd manually before gnomecc,
but it seems that this shouldn't be necessary.  I should also say that I did
get it to sync once, with I think 0.1.46.  But over the past 3 releases almost
every time I've been getting this type of behavior.

Thanks for your response,
Dan