Re: GPILOTD and EVOLUTION Crash!

[Matt Davey <mcdavey mrao cam ac uk>]

On Tue, 2005-06-21 at 18:01, Ro wrote:
> Hey guys. Below is the debug of the problem I'm having using the GPILOTD
> conduits from within Evolution to SYNC with my TREO 600. I have a FRESH
> FC4 installation 

[...]

I've just taken a quick look at the FC4 distribution.

First off, what version of the RPMs do you have, and have you checked
to see if there are updates available?

If there is _anyone_ out there with a success story from FC4, please
speak up, as it's likely to save a bunch of people barking up the
wrong tree.

FC4 has shipped with patched versions of:
	pilot-link-0.12.0-pre2
	gnome-pilot-2.0.13
	evolution-2.2.2

Shipping with the pre-release pilot-link is definitely what I'd call
bleeding edge!  The pilot-link API changes required shipping with
patches to gnome-pilot and the evolution conduits.  I don't know
what level of testing was carried out, but my first suspicion
is that there's something amiss here.

I also noticed that they've _disabled_ the backup conduit,
presumably to avoid problems with the >64k resource bugs,
which I believe have been fixed in the recent pre-release
0.12.0 pilot link versions.

Before digging into this any further, it would be great if you
could manage to recompile gnome-pilot and the evo conduits from
source, without any of the FC4 patches, and see if the problem
goes away.

If that sounds too much, how about more detailed trace info:
See  http://live.gnome.org/GettingTraces for info, and pick
up the debug RPMs for gnome-pilot, pilot-link and evo:
http://ftp.heanet.ie/pub/fedora/linux/core/4/i386/debug/

Matt

Matt Davey		It takes one drink to get me drunk, but I can't 
mcdavey mrao cam ac uk 	     remember if it's the 13th or 14th -- George Burns