Bug#759530: libc-bin: ldconfig breaks a system

[Hagen Fuchs <code@hfuchs.net>]

Package: libc-bin
Version: 2.19-11
Followup-For: Bug #759530

Hello!

Something similar happened to me (after upgrade to 2.19-11).  If this
report wasn't on top of libc-bin and absolutely recent, I would not have
said a word: read on!

Foundation-laying: the scenario.  All packages that call ldconfig in their
install scripts started sputtering like this one:

   Setting up golang (2:1.3.2-1) ...
   Processing triggers for libc-bin (2.19-11) ...
   Segmentation fault
   /sbin/ldconfig.real: Path `/lib/x86_64-linux-gnu' given more than once
   /sbin/ldconfig.real: Path `/usr/lib/x86_64-linux-gnu' given more than once
   /usr/lib/x86_64-linux-gnu/libfakeroot:
           libfakeroot-0.so -> libfakeroot-tcp.so
   /usr/local/lib:
   /lib/x86_64-linux-gnu:
           libthread_db.so.1 -> libthread_db-1.0.so
           [...]
           libglib-2.0.so.0 -> libglib-2.0.so.0.4200.0
   /usr/lib/x86_64-linux-gnu:
   Segmentation fault
   dpkg: error processing package libc-bin (--configure):
    subprocess installed post-installation script returned error exit status 139
   Errors were encountered while processing:
    libc-bin

Hu?  ldconfig dies like this (strace):

   [natural-looking output]
   stat("/usr/lib/x86_64-linux-gnu/libQtScript.so.4", {st_mode=S_IFREG|0644, st_size=2692504, ...}) = 0
   stat("/usr/lib/x86_64-linux-gnu/libjasper.so.1",  <unfinished ...>
   +++ killed by SIGSEGV +++
   Segmentation fault

Oh?

   # file /usr/lib/x86_64-linux-gnu/libjasper.so.1
   Segmentation fault

Drastic measures (wtf?):

   # ls !$
   ls /usr/lib/x86_64-linux-gnu/libjasper.so.1
   Segmentation fault
   # rm /usr/lib/x86_64-linux-gnu/libjasper.so.1
   Segmentation fault
   # unlink !$
   unlink /usr/lib/x86_64-linux-gnu/libjasper.so.1
   # ls /usr/lib/x86_64-linux-gnu/libjasper.so.1
   ls: cannot access /usr/lib/x86_64-linux-gnu/libjasper.so.1: No such file or directory

Done (reinstall libjasper1).

Now, ordinarily, I'd say: severe FS corruption, something or other.
But, with this report on top, perhaps there's something deeper going on.
No idea.

Note: I now have no way of returning to the broken state.

I doubt anyone can profit from this, but I had to throw it in (as I
already mentioned).

Such is my tale of woe.

Regards,
  Hagen