On Thu, 2009-10-15 at 18:31 +0100, Martin Eckart wrote: Using the binaries from syncevolution.org or the recently packaged SyncEvolution from Ubuntu Universe? It comes from SyncContext::getConfigXML(). The XML config is generated on-the-fly. Later it is dumped to the log file, but not at that early stage. Hmm, should we catch config parser errors and dump the content of the config for debugging? <logsessionstoglobal> has been supported in all libsynthesis versions that were packaged for SyncEvolution. The code which checks it is in src/sysync/syncappbase.cpp. However, the real problem might be "Fatal: invalid value in 'values' attribute at line 1001 col 10". Do you think you could compile from source? Attached is a patch which dumps the XML to stdout. It applies to the current master branch, but should also work with the 0.9 sources when you patch the file src/syncevo/EvolutionSyncClient.cpp. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

On Fri, 2009-10-16 at 16:50 +0100, Martin Eckart wrote: It was compiled for Ubuntu Hardy. Whether it works on Jaunty depends on the libs in Jaunty being compatible. We don't test this. Can you compare whether different libs are used? Run "ldd /usr/bin/syncevolution" and then "ldd" on your self-compiled binary. Any relevant differences? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

On Fri, 2009-10-16 at 17:34 +0100, Martin Eckart wrote: We compile with --enable-evolution-compatibility. That avoids hard dependencies on EDS libs, which are know to vary between platforms in ways that rename the library without affecting SyncEvolution otherwise. The original binary? So you compiled as root? Can you reinstall the syncevolution .deb and check whether it still works? The relevant library for XML parsing is libsynthesis.so.0. It's the one which calls libexpat. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

Sorry for the delay, I've been out of town all weekend. The sentence I wrote was vague. Since compiling from source, the original .deb binary also works correctly. I compiled with: ./configure make sudo make install <-- sudo installs as root Removing and reinstalling the .deb still works. I'm still not sure where the discrepancy is. Just ran a test by deleting libsynthesis* and libsmltk* then reinstalling from the .deb and It still works fine. So I don't think those libraries are where the problem was occurring. Hopefully I can find a way to make the problem occur again.

On Mon, 2009-10-19 at 19:18 +0100, Martin Eckart wrote: That sounds possible. I was wondering about the "overwrote system library" part earlier. A configure without explicit --prefix=/usr should install in /usr/local and thus not overwrite anything. I myself don't install as root, by making /usr/local writable for my normal account. checkinstall is even better. It creates .debs which (if named like the ones from syncevolution.org) ensures that no conflicting versions are installed in parallel and/or on top of each other. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.