gnome-pilot doesn't do irda without help

[James D Strandboge <jstrand1 rochester rr com>]

I am using kernel 2.4.20 with a Palm m500 (visor module), gnome2 with
gnome-pilot 0.1.71 and pilot-link 0.11.7.  I also use the backup, memo
and evolution (1.2.1) conduits.

After a reboot, if I try to sync using gpilotd (just from the command
line since gpilotd-applet doesn't work with gnome2 yet) then all I get
from gpilotd is (after pressing the hotsync button):
 
gpilotd-Message: Watching Infrared (/dev/ircomm0)

When the palm time's out, I press ok on the palm, then get:

gpilotd-Message: Woke on Infrared
gpilotd-Message: setting PILOTRATE=115200

gpilotd-WARNING **: pi_accept_to: Connection timed out

gpilotd-WARNING **: pi_accept_to: timeout was 60 secs
gpilotd-Message: Restarting irda funk...
gpilotd-Message: Watching Infrared (/dev/ircomm0)

The above repeats if I press Hotsync.  Killing gpilotd makes no
difference.  However, if I use other pilot software first, then from
that point forward I can use gpilotd.  Eg:

killall gpilotd
rm ~/.gpilotd.pid
pilot-xfer -p /dev/ircomm0 -l &
sleep 5
killall pilot-xfer
gpilotd

Now the syncing works with gnome-pilot perfectly (and I don't have to do
the above until after a reboot).  Notice that I don't have to sync with
pilot-xfer (I kill it without pressing Hotsync on the palm), I just have
to run the program for a few seconds.  USB syncing does not have this
problem.  

It is like gnome-pilot isn't initializing itself and/or the port
somehow.  jpilot doesn't have this problem.  

The device is configures with:
device: /dev/ircomm0
rate: 115200
timeout: 60

Any help is appreciated and I would be happy to send any additional
information.

BTW-- where is the gnome2 port?  I saw a thread back in April 2002, but
nothing else.

Thanks,

James Strandboge

-- 
Email:        jstrand1 rochester rr com
GPG/PGP ID:   26384A3A
Fingerprint:  D9FF DF4A 2D46 A353 A289  E8F5 AA75 DCBE 2638 4A3A