On Sat, 2015-05-30 at 08:43 +0200, Daniel CLEMENT wrote: > Le vendredi 29 mai 2015 à 22:13 +0200, Patrick Ohly a écrit : > > On Fri, 2015-05-29 at 17:56 +0200, Daniel CLEMENT wrote: > > I'm very suspicious about the binary that you are running on this > > upgraded PC. Please check that it really comes from the official .deb: > > > > which syncevolution > > file `which syncevolution` > > md5sum `which syncevolution` > > dpkg -S `which syncevolution` > > > > Assuming that you are on amd64 (aka 64 bit), that should give: > > > > $ which syncevolution > > /usr/bin/syncevolution > > $ file `which syncevolution` > > /usr/bin/syncevolution: ELF 64-bit LSB executable, x86-64, version 1 > > (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for > > GNU/Linux 2.6.15, > > BuildID[sha1]=05708d05d234df537c464157b331ddb901d52600, not stripped > > $ md5sum `which syncevolution` > > c0405aa56a9976159386c54b7ac47ae1 /usr/bin/syncevolution > > $ dpkg -S `which syncevolution` > > syncevolution-bundle: /usr/bin/syncevolution > > > I get precisely that. Same thing on the older PC.
So it must be some of libraries that the executable is linked against which has the hard dependency on libical.so.0. Try this: LD_TRACE_LOADED_OBJECTS=1 LD_DEBUG=files syncevolution 2>&1 | grep -C2 libical I get no output here because the main executable and none of its direct dependencies uses libical. In your case, I'd expect to see an explanation for the "error while loading shared libraries: libical.so.0". -- 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
