Comment 1 for bug 201724

http://ubuntuforums.org/showthread.php?t=722886

2008/3/13, Jon Lund Steffensen <email address hidden>:
>
> *** This bug is a duplicate of bug 201673 ***
> https://bugs.launchpad.net/bugs/201673
>
> Public bug reported:
>
> Binary package hint: libc6-i686
>
> Upgrade from libc6-i686-2.7-5ubuntu2 to libc-i686-2.7-9ubuntu1 failed
> with a segfault. This somehow left libc in an unusable state. Most
> programs I try to run aborts with glibc errors like:
>
> $ sudo synaptic
> *** glibc detected *** sudo: free(): invalid pointer: 0xb7f96b28 ***
> [...]
>
> and
>
> $ bash
> malloc: unknown:0: assertion botched
> free: called with unallocated block argument
> Aborting...Aborted (core dumped)
>
> Is there any way to go back to the previous version of libc6-i686
> without using sudo?
>
> ** Affects: glibc (Ubuntu)
> Importance: Undecided
> Status: New
>
> --
> libc6 upgrade destroyed my system; everything aborts
> https://bugs.launchpad.net/bugs/201724
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 201673).
>
> Status in Source Package "glibc" in Ubuntu: New
>
> Bug description:
> Binary package hint: libc6-i686
>
> Upgrade from libc6-i686-2.7-5ubuntu2 to libc-i686-2.7-9ubuntu1 failed with
> a segfault. This somehow left libc in an unusable state. Most programs I try
> to run aborts with glibc errors like:
>
> $ sudo synaptic
> *** glibc detected *** sudo: free(): invalid pointer: 0xb7f96b28 ***
> [...]
>
> and
>
> $ bash
> malloc: unknown:0: assertion botched
> free: called with unallocated block argument
> Aborting...Aborted (core dumped)
>
> Is there any way to go back to the previous version of libc6-i686 without
> using sudo?
>