Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
Package: libc6 Version: 2.13-5 Severity: critical Justification: breaks the whole system While upgrading from libc6 2.13-4 to 2.13-5 on a i386 system: Preparing to replace libc6 2.13-4 (using .../archives/libc6_2.13-5_i386.deb) ... Unpacking replacement libc6 ... Setting up libc6 (2.13-5) ... Installing new version of config file /etc/ld.so.conf.d/i486-linux-gnu.conf ... Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! bad dynamic tag' failed! Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! bad dynamic tag' failed! E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/bin/debsums ]; then /usr/bin/debsums --generate=nocheck -sp /var/cache/apt/archives; fi' E: Sub-process returned an error code E: Sub-process /usr/bin/dpkg returned an error code (127) After this no dynamically linked program on the system is startable anymore: haegar:~# dpkg --help Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! bad dynamic tag' failed! haegar@aurora:~$ ls Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! bad dynamic tag' failed! -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.38-sdinet14-aurora (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libc6 depends on: ii libc-bin 2.13-4 Embedded GNU C Library: Binaries ii libgcc1 1:4.6.0-11 GCC support library Versions of packages libc6 recommends: ii libc6-i6862.13-4 Embedded GNU C Library: Shared lib Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.39 Debian configuration management sy ii glibc-doc 2.13-4 Embedded GNU C Library: Documentat ii locales 2.13-4 Embedded GNU C Library: National L -- debconf-show failed -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607140411.6858.77273.reportbug@aurora.local
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
Hi Sven, Sven-Haegar Koch wrote: While upgrading from libc6 2.13-4 to 2.13-5 on a i386 system: Preparing to replace libc6 2.13-4 (using .../archives/libc6_2.13-5_i386.deb) ... Unpacking replacement libc6 ... Setting up libc6 (2.13-5) ... Installing new version of config file /etc/ld.so.conf.d/i486-linux-gnu.conf ... Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! bad dynamic tag' failed! Very odd. That assertion doesn't exist in current glibc; in fact, it was was removed in glibc 2.3! (cvs/glibc-2-3~925, elf/dynamic-link.h (elf_get_dynamic_info): Don't abort on unknown dynamic tags, 2002-04-03). But it was in an inline function in that header, so if some binary package was built on a machine with ancient libc6-dev, that could be a half-explanation. Where do you get your binary packages from? Puzzled, Jonathan -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607144656.GA13080@elie
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
Just to confirm that Sven is not alone, I was hit by the same bug.
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
Dima wrote: Just to confirm that Sven is not alone, I was hit by the same bug. Thanks. To be clear, that means you are also on i386 and also trigger the ! bad dynamic tag assertion on upgrade from 2.13-4 to 2.13-5? I tried reproducing this in a debian-live i386 installation but I didn't manage (the upgrade to libc6-i686 2.13-5 proceeded without trouble). What I said before about libc6-dev was nonsense; elf/dynamic-link.h is a file in the eglibc source package, which makes this all the more puzzling (how was this assertion from more than 5 years ago resurrected?). Probably I am missing something obvious. :) -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607154947.GA24770@elie
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
Thanks. To be clear, that means you are also on i386 and also trigger the ! bad dynamic tag assertion on upgrade from 2.13-4 to 2.13-5? That's right. I'm still logged into the box remotely, but I can not start any new processes. Regards, Dima.
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
But it was in an inline function in that header, so if some binary package was built on a machine with ancient libc6-dev, that could be a half-explanation. Where do you get your binary packages from? ftp.de.debian.org I also get my packages from ftp.de.debian.org But the system has been updated on Debian Unstable since Debian Woody (and moved from PC to PC, from harddisk to harddisk, without reinstall). Mine is also quite old, I've been running unstable for the last 10 years. Regards, Dima.
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
On Tue, 7 Jun 2011, Dima wrote: But it was in an inline function in that header, so if some binary package was built on a machine with ancient libc6-dev, that could be a half-explanation. Where do you get your binary packages from? ftp.de.debian.org I also get my packages from ftp.de.debian.org But the system has been updated on Debian Unstable since Debian Woody (and moved from PC to PC, from harddisk to harddisk, without reinstall). Mine is also quite old, I've been running unstable for the last 10 years. Just to verify - could you check if you also have got an /lib/ld.so file? As you wrote that you are still logged into it you should be able to do the following: $ cd /lib $ echo ld* (and then looking in the output) c'ya sven-haegar -- Three may keep a secret, if two of them are dead. - Ben F. -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.DEB.2.02.1106071842300.27505@aurora
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
As you wrote that you are still logged into it you should be able to do the following: $ cd /lib $ echo ld* Here is is: $ echo ld* ld-2.2.5.so ld-linux.so.1.8.10 ld-linux.so.2 ld.so ld.so.1.8.10
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
I believe I hit the same bug on amd64. After upgrading, all commands fail with error while loading shared libraries: /lib/x86_64-linux-gnu/libc.so.6: unexpected PLT reloc type 0x25. /lib/ld-linux-x86-64.so.2 is pointing to a rather old ld-lsb-x86-64.so.3, changing it to point to x86_64-linux-gnu/ld-2.13.so fixes the problem. Regards, -Atte -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTina_U69e73=aawark+xp7klvo8...@mail.gmail.com
Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore
retitle 629534 Upgrade fails, resulting in unusable system (no dynamic linking) thank you On Tue, 7 Jun 2011 10:49:48 -0500, Jonathan Nieder jrnie...@gmail.com wrote: Just to confirm that Sven is not alone, I was hit by the same bug. Me too! Thanks. To be clear, that means you are also on i386 and also trigger the ! bad dynamic tag assertion on upgrade from 2.13-4 to 2.13-5? I am also on i386 and also hit the failure on upgrade from 2.13-4 to 2.13-5. I did not see the bad dynamic tag assertion failure. Elsewhere in the thread was discussion of old linkers in /lib. I had that as well: /lib$ echo ld* ld-2.7.so ld-linux.so.2 I was able to fix my system by booting to a live USB, mounting my filesystem and updating that symlink: ln -sf i386-linux-gnu/ld-2.13.so /lib/ld-linux.so.2 I saw that some people were having trouble replicating the upgrade failure. In case it helps, here is the upgrade history I was able to find for the libc6 package on my system: 2010-10-12: libc6:i386 (2.11.2-5, 2.11.2-7) 2011-01-11: libc6:i386 (2.11.2-6, 2.11.2-7) 2011-05-23: libc6:i386 (2.11.2-7, 2.11.2-11) 2011-05-05: libc6:i386 (2.11.2-11, 2.13-2) 2011-05-24: libc6:i386 (2.13-2, 2.13-4) Please let me know if there's any further information I can provide. -Carl -- carl.d.wo...@intel.com pgpNsxQwKUt0r.pgp Description: PGP signature
