On Wed, 2015-05-27 at 17:51 +0200, Daniel CLEMENT wrote: > Le mercredi 27 mai 2015 à 17:34 +0200, Patrick Ohly a écrit : > > On Wed, 2015-05-27 at 17:21 +0200, Daniel CLEMENT wrote: > > > > > Then e.g. > > > > > syncevolution --sync refresh-from-remote memotoo memo > > > > > gives me an error code 10508: > > > > > > > > > > [...] > > > > > > > > What further details does that file have about the 508 error? > > > > > > > > > > Below is the end of the log file, from the point where the 508 error > > > appears: > > > ----- > > > – > > > [2015-05-27 16:57:51.582] 'SessionAbort' - Aborting Session, > > > Status=508, > > > ProblemSource=LOCAL [--][++] [->end] [->enclosing] > > > > What's above it? That's where the real issue should be logged. You may > > have to run with loglevel=4 to see more. > > > Hope I didn't mess up the command line, here is what I did: > syncevolution --run loglevel@memotoo=4 --sync refresh-from-remote > memotoo memo > > I'm attaching the log file (the copy/paste doesn't look good in plain > text).
Reading calendar items seems to fail, with no obvious error logging at all. Does "LD_DEBUG=1 syncevolution --daemon=no --print-items memotoo memo" show anything? Do you have memos locally? Do you perhaps still have obsolete EDS libraries installed? Try this: for i in /usr/lib/syncevolution/backends/syncecal*.so; do echo $i; if ldd $i | grep -q "not found"; then echo " unusable"; else echo " usable"; fi; done syncevolution --daemon=no --version On my own Debian installation, I somehow ended up with syncecal-4.so and syncecal-5.so as usable. syncecal-5.so is the version which gets picked, which happens to match libecal-1.2.so.16 because both use libical.so.1. syncecal-4.so is usable because I had an obsolete libical.so.0 installed which wasn't used anymore by anything and could be removed. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
