Le jeudi 28 mai 2015 à 10:01 +0200, Patrick Ohly a écrit :
[...]
> >
> 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.
Memos "almost" worked. I erased
~/.local/share/evolution/memos/system/journal.ics and then I could
perform a refresh-from-remote sync, only for memos, which successfully
recreated the above file. But the subsequent attempts failed.
And I could not do the same with the calendar.ics file.
Does "LD_DEBUG=1 syncevolution --daemon=no --print-items memotoo memo"
show anything?
The result looks correct:
daniel@e6330d ~ $ LD_DEBUG=1 syncevolution --daemon=no --print-items
memotoo memo
warning: debug option `1' unknown; try LD_DEBUG=help
syuid131753%2e212299596272388-rid: Logitech Harmony :
syuid247279%2e212299596272398-rid: NUMEN :
syuid295660%2e212299596272393-rid: Livres
syuid408817%2e212299596272365-rid: E-mail jetable
syuid409316%2e212299596272406-rid: Quickstep
syuid458695%2e212299596272416-rid: Naissance Parents :
syuid633486%2e212299596272346-rid: Clés autos
syuid696773%2e212299596272358-rid: Caractéristiques de ...
syuid697395%2e212299596272441-rid: Papier peint
syuid699214%2e212299596272383-rid: Courbes périlleuses
syuid771910%2e212299596272378-rid: Piles montres
syuid781737%2e212299596272412-rid: Films à rechercher :
syuid797248%2e212299596272420-rid: Scolinfo
syuid806450%2e212299596272424-rid: e-CB
syuid836056%2e212299596272372-rid: Pour les lavabos :
syuid898450%2e212299596272428-rid: MAIF (sinistres) :
syuid916864%2e212299596272436-rid: Livres
syuid941545%2e212299596272402-rid: Diagral :
syuid951393%2e212299596272432-rid: Adresse plan Google
Do you have memos locally?
Yes, they match the above list.
Do you perhaps still have obsolete EDS libraries installed?
Quite possible, at least because at first I was using the Debian
repository, before adding the Syncevolution repository.
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
daniel@e6330d ~ $ 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
/usr/lib/syncevolution/backends/syncecal-2.so
usable
/usr/lib/syncevolution/backends/syncecal-3.so
usable
/usr/lib/syncevolution/backends/syncecal-4.so
usable
/usr/lib/syncevolution/backends/syncecal-5.so
usable
/usr/lib/syncevolution/backends/syncecal.so
usable
It makes a whole lot, though everything is "usable". Could it be the
problem? Should I do some cleanup there?
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.
To be precise, I am running Linux Mint Debian, which is now (after the
upgrade) identical to Debian Stable (aka Jessie now), except for some
Mint-desktop specific packages. For all the Gnome stuff like Evolution,
there is no difference.
--
Daniel CLEMENT