Bug#817960: libc6: relocation error version GLIBC_PRIVATE not defined in file libc.so.6
On 2016-03-12 14:04, ಚಿರಾಗ್ ನಟರಾಜ್ wrote:
> On Sat, Mar 12, 2016 at 12:15:13PM +0100, Aurelien Jarno wrote:
> > Could you please give us the exact error message you encountered,
> > including the symbol name (a photo is fine), so that we can narrow down
> > the problem? At a first glance it looks like the libc has been partially
> > upgraded, and that you now have a mix of both 2.21 and 2.22.
>
> I have attached a screenshot of what I'm getting (I made a LVM
> snapshot this time and tried to upgrade the snapshot so it didn't
> hose my actual system). It conks out when it's processing
> triggers for man-db.
Thanks for your screenshot, it definitely helps. The symbol
h_errno@GLIBC_PRIVATE has been renamed into __h_errno@GLIBC_PRIVATE in
glibc 2.22.
Normally if you use both libpthread.so.0 and libc.so.6 from glibc 2.21
and glibc 2.22 everything should work. In your case it seems after the
upgrade you end up with libc.so.6 from glibc 2.21 (instead of 2.22)
while libpthread.so.0 is from glibc 2.22. It might be you have a copy if
libc.so.6 somewhere in the locations ld.so is search for.
Could you therefore please send me the output of "ldd /bin/ls" before
upgrading your system? That should give something like that:
linux-vdso.so.1 (0x00007ffe1013f000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f836df6f000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f836dbcb000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f836d95a000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f836d756000)
/lib64/ld-linux-x86-64.so.2 (0x0000562bc2437000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f836d539000)
You should check if the libc.so.6 which is used is the one from
/lib/x86_64-linux-gnu or if another one is used.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: