On Thu, Mar 26, 2009 at 11:31:21AM +0100, Daniel Gollub wrote:
> Interesting - last night someone on IRC had exactly the same problem...
>
http://pastebin.ca/1372538>
> Could you try attached patch?
Sorry, I should have mentioned it... that was me on IRC :-)
The patch seemed to work at the time, and I added a ticket for it,
but later on, I got other similar crashes. Sometimes hard to reproduce
reliably.
> > I just want to know I'm not crazy. :-) If other people are using it on
> > Debian Lenny, I'd dearly love to know your config.
>
> Looks like you're not alone - it's working for me. But i'm running openSUSE 11.1.
> The guy from last night was also using lenny - but he wasn't sure if his installation was
> "clean". But since you're within 12h the second guy i guess their is an issue with the recent
> packaging or recent version of evolution or e-d-s.
>
> Which exactly version of evolution and e-d-s and libgconf are you running?
Last night, I went through removing e-d-s related packages and installing
fresh ones from lenny. So now I'm sure I'm using a set of devel libraries
(evolution-data-server-dev, libedataserver1.2, libebook1.2, etc) all
with the same version of 2.22.3-1.1.
All Lenny versions of opensync 0.22 are removed as well, but I don't think
that was having an effect.
Is there a document somewhere that describes the internal architecture
of the opensync library? It seems to create a lot of threads, which
appear to be used for message passing. It is almost always in these
threads where the crashes occur (which makes some sense, if the crash
happens in the evolution plugin).
Thanks,
- Chris
------------------------------------------------------------------------------
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel