Le samedi 30 mai 2015 à 13:30 +0200, Patrick Ohly a écrit :
> 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".
>
>
There's a lot of output here:
daniel@e6330d ~ $ LD_TRACE_LOADED_OBJECTS=1 LD_DEBUG=files syncevolution
2>&1 | grep -C2 libical
3617:
3617:
3617: file=libical.so.0 [0]; needed
by /usr/local/lib/libsynthesis.so.0 [0]
3617: file=libical.so.0 [0]; generating link map
3617: dynamic: 0x00007f2a7a9bfd60 base: 0x00007f2a7a760000
size: 0x0000000000262340
3617: entry: 0x00007f2a7a77bdb0 phdr: 0x00007f2a7a760040
phnum: 7
3617:
3617:
3617: file=libicalss.so.0 [0]; needed
by /usr/local/lib/libsynthesis.so.0 [0]
3617: file=libicalss.so.0 [0]; generating link map
3617: dynamic: 0x00007f2a7a75ccf0 base: 0x00007f2a7a547000
size: 0x0000000000218888
3617: entry: 0x00007f2a7a54f9e0 phdr: 0x00007f2a7a547040
phnum: 7
3617:
3617:
3617: file=libicalvcal.so.0 [0]; needed
by /usr/local/lib/libsynthesis.so.0 [0]
3617: file=libicalvcal.so.0 [0]; generating link map
3617: dynamic: 0x00007f2a7a543ce0 base: 0x00007f2a7a331000
size: 0x0000000000215168
3617: entry: 0x00007f2a7a337f10 phdr: 0x00007f2a7a331040
phnum: 7
--
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f2a7ac8c000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
(0x00007f2a7a9c3000)
libical.so.0 => /usr/lib/libical.so.0 (0x00007f2a7a760000)
libicalss.so.0 => /usr/lib/libicalss.so.0 (0x00007f2a7a547000)
libicalvcal.so.0 => /usr/lib/libicalvcal.so.0 (0x00007f2a7a331000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f2a7a116000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2
(0x00007f2a79daf000)
In particular, what's this libsynthesis.so.0 in /usr/local/lib? Is that
again a residue of the patched version that I had compiled once on this
PC?
Under /usr/local/lib I still have these libsynthesis* files:
libsynthesis.a
libsynthesis.la
libsynthesissdk.a
libsynthesissdk.la
libsynthesis.so
libsynthesis.so.0
libsynthesis.so.0.6.0
libsynthesisstubs.a
libsynthesisstubs.la
which I had forgotten here because everything went well under the old
Linux Mint Debian. Are they the cause of all this trouble?
--
Daniel CLEMENT
_______________________________________________
SyncEvolution mailing list
[email protected]
https://lists.syncevolution.org/mailman/listinfo/syncevolution
