[Evolution] Having problems with gpilotd all of a sudden

[Mike Godfrey <migod uwaterloo ca>]

Greetings,

Am using evo 1.2.2 on redhat 9 (stock version from redhat 9, with
security update).  This includes gnome-pilot-0.1.71-2.

I have been using the combo successfully for a while now, but suddenly,
gpilotd is misbehaving.  If I click on evo Tools -> Pilot Settings, and
then press Cancel, I get this output usually as gpilotd dumps core:

> Message: Pilot name -> MyClie-NX70V
> Message: Pilot id   -> 21050
> Message: Pilot username -> migod
> Message: Pilot creation/rom = 0/0
> Message: Pilot sync_action -> not_set
> Message: Cradle Type -> USB
> Message: cradle device name -> ClieCradle
> Message: cradle device name -> /dev/Clie
> Message: Pilot Speed  -> 115200
> Message: Timeout -> 2
> gpilotd-Message: Initing gnome vfs
> gpilotd-Message: gnome-pilot 0.1.71 starting...
> gpilotd-Message: compiled for pilot-link version 0.11.5
> gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
> gpilotd-Message: Activating CORBA server
> Message: pilot = MyClie-NX70V
> gpilotd-Message: Watching ClieCradle (/dev/Clie)
> gpilotd-Message: gpilotd: Client seems ok
> gpilotd-Message: gpilotd: Client seems ok
> gpilotd-Message: gpilotd: monitor_on(pilot_name="MyClie-NX70V",client_id = IOR:010000001b000000...)
> gpilotd-Message: gpilotd: corba: notify_on(event_type=CONNECT,callback=IOR:010000001b000000...)
> gpilotd-Message: gpilotd: corba: notify_on(event_type=DISCONNECT,callback=IOR:010000001b000000...)
> Message: Pilot name -> MyClie-NX70V
> Message: Pilot id   -> 21050
> Message: Pilot username -> migod
> Message: Pilot creation/rom = 0/0
> Message: Pilot sync_action -> not_set
> Message: Cradle Type -> USB
> Message: cradle device name -> ClieCradle
> Message: cradle device name -> /dev/Clie
> Message: Pilot Speed  -> 115200
> Message: Timeout -> 2
> gpilotd-Message: Exiting (caught SIGTERM)...

Sometimes, tho, it doesn't dump core, but when I try to sync, I get this
warning:

> gpilotd-WARNING **: pi_accept_to: Connection timed out
> gpilotd-WARNING **: pi_accept_to: timeout was 2 secs

This was working yesterday, really!

I've tried killev, oaf-slay, and even rebooting.

[Oddly, I can sync through Linux to WinXP using vmware just fine.  Yes,
I know I have to rmmod visor to make it work; I'm an old hand at
dual-syncing.  You can read about it on my web page if you like:
> http://plg.uwaterloo.ca/~migod/techie/clieLinux.html
]

-- Mike