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

Bug#555205: marked as done (libc6: segfault when upgrading from 2.9-25 -> 2.10.1-5 on squeeze renders system unusable)

Your message dated Sun, 27 Jun 2010 07:45:56 +0200
with message-id <20100627054556.GA30036@ohm.aurel32.net>
and subject line Re: Bug#555205: segfault caused by optimized library?
has caused the Debian Bug report #555205,
regarding libc6: segfault when upgrading from 2.9-25 -> 2.10.1-5 on squeeze renders system unusable
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.)


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


I tried to upgrade to the current "testing" version of libc6: 2.10.1-5

Below is the output from aptitude:

-----
Preparing to replace libc-bin 2.9-25 (using .../libc-bin_2.10.1-5_i386.deb) ...
Unpacking replacement libc-bin ...
Processing triggers for man-db ...
Setting up libc-bin (2.10.1-5) ...
(Reading database ... 56540 files and directories currently installed.)
Preparing to replace libc6 2.9-25 (using .../libc6_2.10.1-5_i386.deb) ...
Checking for services that may need to be restarted...
Checking init scripts...
Unpacking replacement libc6 ...
Setting up libc6 (2.10.1-5) ...
dpkg: error processing libc6 (--configure):
 subprocess installed post-installation script killed by signal (Segmentation fault)
Errors were encountered while processing:
  libc6
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 (1)
-----

I was upgrading this system remotely (bad, yes, I know) and could no
longer enter any commands. Every command would return a "segmentation
fault."

Rebooting the system did not help either. I ultimately had to boot into
another OS and copy back the files from version 2.9-25 in order to have
a usable system.

I can try to provide additional details if necessary.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6 depends on:
ii  libc-bin                      2.9-25     GNU C Library: Binaries
ii  libgcc1                       1:4.4.1-4  GCC support library

Versions of packages libc6 recommends:
di  libc6-i686                    2.9-25     GNU C Library: Shared libraries [i

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]         1.5.28     Debian configuration management sy
pn  glibc-doc                     <none>     (no description available)
ii  locales                       2.9-25     GNU C Library: National Language (

-- debconf information:
* glibc/upgrade: true
  glibc/disable-screensaver:
  glibc/restart-failed:
* glibc/restart-services: spamassassin ssh saslauthd rsync openbsd-inetd mysql dovecot exim4 cron courier-authdaemon atd

--- End Message ---
--- Begin Message --- 
On Sat, Jun 26, 2010 at 12:33:37PM -0400, bjn wrote:
> On Sat, 26 Jun 2010, deb wrote:
> 
> >Hello,
> >
> >I want to know if the bug is closed. I still see this msg:
> >
> >critical bugs of libc6 (2.9-23em1 -> 2.11.2-2) <unfixed>
> >  #555205 - libc6: segfault when upgrading from 2.9-25 -> 2.10.1-5
> >on squeeze renders system unusable
> >
> 
> I am the original reporter of the bug. I don't know if this bug was
> ever technically fixed, but I've since upgraded to a more recent
> version of libc6 without a problem.
> 
> As far as I'm personally concerned, the bug can be closed.
> 

Thanks for the feedback, I am closing the bug with this email.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: