Re: GPILOTD Memofile Sync crash

[Jim Robinson <jim sngcworld com>]

Confirmed.  This crashed again with the settings in place.  I also tried
a number of combinations for the path name and they all ended up seg.
faulting gpilotd. 

I have been digging through the log files and noted this in messages:
Jul 17 09:47:24 lsp-bench kernel: usbserial.c: Handspring Visor / Treo /
Palm 4.0 / Cli? 4.x converter now attached to ttyUSB0 (or usb/tts/0 for
devfs)

Jul 17 09:47:24 lsp-bench kernel: usbserial.c: Handspring Visor / Treo /
Palm 4.0 / Cli? 4.x converter now attached to ttyUSB1 (or usb/tts/1 for
devfs)

I am using a Palm m500 - should it be grabbing both USB channels?  Not
sure if this is relevant but I thought I would through it out there. 
Any info I can provide just let me know.

Jim 


On Wed, 2003-07-16 at 11:03, Nigel Metheringham wrote:
> On Wed, 2003-07-16 at 15:33, JP Rosevear wrote:
> > On Wed, 2003-07-09 at 13:58, Jason 'vanRijn' Kasper wrote:
> > > unfortunately, it's a known bug. I also sent an e-mail to this list just
> > > a couple of weeks ago asking about the same bug and heard absolutely
> > > nothing in reply.  I'm wondering if any of the developers for
> > > gnome-pilot frequent this list.
> > 
> > I have it fixed in my local tree (not to crash any how).  The crash is
> > because you are not specifying a directory for the conduits in the
> > settings.
> 
> Odd.  I have tried the memofile conduit both with a relative (to my
> overall palm directory) and absolute directory in the memofile conduit
> settins, with and without the directory pre-existing, and it still
> crashes.  Every time.
> 
> 	Nigel.
> 
> PS welcome back from vacation - at least the huge pile of bugzilla
> reports and mail lets you know you have been missed!