On Wed, 14 Sep 2005 00:09:25 +0200, Florian Ernst wrote:
> Hello *,
>
> On Tue, Sep 13, 2005 at 05:29:55PM -0400, Tong wrote:
>> Today, I did my routine apt-get upgrade and noticed that the libc has been
>> updated. However, now apt-get upgrade fails to configure the updated
>> package. The error message is:
>>
>> Preconfiguring packages ...
>> *** glibc detected *** double free or corruption (!prev): 0x0893e320 ***
>> /bin/sh: line 1: 6046 Aborted /usr/sbin/dpkg-preconfigure
>> --apt
>> Setting up debconf (1.4.58) ...
>> *** glibc detected *** double free or corruption (!prev): 0x088d9240 ***
>> dpkg: error processing debconf (--configure):
>> subprocess post-installation script killed by signal (Aborted)
>> Errors were encountered while processing:
>> debconf
>> [...]
>
> <http://bugs.debian.org/322746> contains a detailed error description
Thank you Florian for the prompt reply.
> as well as a workaround and the solution.
I waded though the lengthy/messy posting and find the solution at last. In
case others interested. The (temp) solution is as follows, as posted by
Jim Van Zandt:
I suggest something like this for recovery:
dpkg-reconfigure debconf
<select some frontend other than readline>
dpkg --configure -a # recover from failed configurations
apt-get install --reinstall sash # recover from even worse corruption
apt-get -t unstable install libterm-readline-gnu-perl # fix basic problem
dpkg-reconfigure debconf
<select readline frontend again>
>> I've reboot but symptom is the same.
>
> Huh, reboot?
Oh, well, a most common panic reaction when you see something
wont-be-broken breaks in front of your eyes. :-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
