On Thu, 2015-05-28 at 12:19 +0200, Daniel CLEMENT wrote:
> Le jeudi 28 mai 2015 à 11:26 +0200, Patrick Ohly a écrit :
> > On Thu, 2015-05-28 at 11:22 +0200, Daniel CLEMENT wrote:
> > > Le jeudi 28 mai 2015 à 10:01 +0200, Patrick Ohly a écrit :
> > > > 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?
> > 
> > It would be a good start. Something is messed up in your EDS
> > installation if you can create the memo.ics file, but then not read it
> > again.
> Hmm... I could check that all of the above libraries are part of the
> syncevolution-bundle package, which of course I want to keep.

That's not what I meant. When you run
"ldd /usr/lib/syncevolution/backends/syncecal-3.so | grep ecal" it will
point you to a libecal version that belongs to an obsolete EDS.

Check in aptitude under "obsolete" packages, or use "dpkg -S" to locate
the owner of that libecal*.so*. Get rid of those.

Same for all other obsolete /usr/lib/libe*.*so* files.

-- 
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

Reply via email to