Bug#383976: unable to upgrade package libc6

[Aurelien Jarno <aurelien@aurel32.net>]

Hi,

On Mon, Aug 21, 2006 at 10:15:10AM +0200, Tomasz Cichecki wrote:
> Package: libc6
> Version: 2.3.6-19
> Severity: grave
> Justification: renders package unusable
> 
> I cannot upgrade from libc6_2.3.6-19 to libc6_2.3.6.ds1-2
> Below screen dump:
> knight@workingrock:/usr/share/doc/libc6$ export LC_ALL=C
> knight@workingrock:/usr/share/doc/libc6$ sudo apt-get install libc6
> Reading package lists... Done
> Building dependency tree... Done
> Suggested packages:
>   glibc-doc
>   The following packages will be upgraded:
>     libc6
>     1 upgraded, 0 newly installed, 0 to remove and 93 not upgraded.
>     1 not fully installed or removed.
>     Need to get 0B/4696kB of archives.
>     After unpacking 0B of additional disk space will be used.
>     (Reading database ... 175620 files and directories currently
>     installed.)
>     Preparing to replace libc6 2.3.6-19 (using
>     .../libc6_2.3.6.ds1-2_i386.deb) ...
>     Unpacking replacement libc6 ...
>     dpkg: error processing
>     /var/cache/apt/archives/libc6_2.3.6.ds1-2_i386.deb (--unpack):
>      dpkg: warning - old post-removal script killed by signal
>      (Segmentation fault)
> 
>    dpkg: error while cleaning up:
>     subprocess pre-installation script killed by signal (Segmentation
>     fault)
>    Errors were encountered while processing:
>      /var/cache/apt/archives/libc6_2.3.6.ds1-2_i386.deb
>    E: Sub-process /usr/bin/dpkg returned an error code (1)
 
I am unable to reproduce this problem on my machine, so we will have to
debug it on our system.

First of all, is your system ok? Random segfaults could come for a
kernel that started to oops. You can have a look to the output of 
"dmesg".

Then, it would be nice to know which program in the posrtm/preinst fail.
You can try to look at the output of "dmesg", sometimes programs that
segfault are written there. If this is not the case, you can change the
first line of /var/lib/dpkg/info/libc6.postrm from
  ! /bin/sh
to
  ! /bin/sh -x
, try to upgrade again and send me the output. 

Finally it would be nice if you acn send me the output of "ldd
/bin/bash", so that we can see which version of the libc are you using
(linuxthreads, nptl, nptl i686 or xen).

Bye,
Aurelien

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net