[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#817960: marked as done (libc6: relocation error version GLIBC_PRIVATE not defined in file libc.so.6)

Your message dated Sat, 12 Mar 2016 18:31:03 +0100
with message-id <20160312173103.GA31073@aurel32.net>
and subject line Re: Bug#817960: libc6: relocation error version GLIBC_PRIVATE not defined in file libc.so.6
has caused the Debian Bug report #817960,
regarding libc6: relocation error version GLIBC_PRIVATE not defined in file libc.so.6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
817960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817960
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6
Version: 2.22-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

When I upgrade from libc6 2.21-9 to 2.22-2, I get the error "relocation error version GLIBC_PRIVATE not defined in file libc.so.6" whenever I launch most programs (sed, grep, ls, etc.) and the program fails to start. This extends to booting up and so the system is unbootable.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc7-chiraag (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On 2016-03-12 16:21, ಚಿರಾಗ್ ನಟರಾಜ್ wrote:
> On Sat, Mar 12, 2016 at 04:50:17PM +0100, Aurelien Jarno wrote:
> > 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.
> Looks like that fixed it!

Thanks for the feedback, I am therefore closing the bug.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: