Re: gpilotd crashes all the time when sync'ing via IrDA

[Alan Shutko <ats acm org>]

Eloy Paris <eparis@andrew.cmu.edu> writes:

> I just wanted to mention that gpilotd seems to crash all the time when
> I am sync'ing via IrDA (IrCOMM). Since I can reliable reproduce this,
> please do not hesitate to contact me if you need more information.

Ditto.  There are a few more of us... search the gnome-pilot bugs for
more info and backtraces.

We're dying in device_err after a successful sync with condition=24
(iirc).  This happens after the sync has completed.  It immediately
wakes up again, thinking that I'm syncing again (which I'm not).  I
started to look into it, but this is as far as I've gotten so far.
Here's the output:

gpilotd-Message: Synchronization ended
Message: memo_file: destroying memo_file conduit
gpilotd-Message: gpilotd: corba: orbed_notify_user, notifications->disconnect.size = 1, id = MyPilot
gpilotd-Message: Woke on Cradle
gpilotd-Message: setting PILOTRATE=115200

gpilotd-WARNING **: pi_accept: Connection timed out

gpilotd-WARNING **: Device error on Cradle (/dev/pilot), caught unhandled port error
gpilotd-Message: Removing Cradle
gpilotd-Message: Rereading configuration...
gpilotd-Message: Watching Cradle (/dev/pilot)


-- 
Alan Shutko <ats@acm.org> - In a variety of flavors!
101 days, 21 hours, 54 minutes, 3 seconds till we run away.
If rabbits' feet are so lucky, what happened to the rabbit?