Hi,
Could this bug be caused by a corrupt aux-cache[1] (possibly, in
addition to a corrupt ld.so.cache)?
A bit of google searching suggests that a broken aux-cache can cause
ldconfig to seg. fault. With the ld.so.cache itself being corrupt (or
sufficiently outdated?), both ldconfig and most othe
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 ldconf
Aurelien Jarno writes:
> On Thu, Aug 28, 2014 at 10:07:57AM +0400, Dmitrii Kashin wrote:
>> Package: libc-bin
>> Version: 2.19-9
>> Severity: grave
>> File: /sbin/ldconfig
>>
>> Dear Maintainer,
>>
>> I had an upgrade of libc6 and libc-bin packages up to the version
>> 2.19-9 from 2.19-4 while
On Thu, Aug 28, 2014 at 10:07:57AM +0400, Dmitrii Kashin wrote:
> Package: libc-bin
> Version: 2.19-9
> Severity: grave
> File: /sbin/ldconfig
>
> Dear Maintainer,
>
> I had an upgrade of libc6 and libc-bin packages up to the version
> 2.19-9 from 2.19-4 while executing `apt-get upgrade'. In the
Package: libc-bin
Version: 2.19-9
Severity: grave
File: /sbin/ldconfig
Dear Maintainer,
I had an upgrade of libc6 and libc-bin packages up to the version
2.19-9 from 2.19-4 while executing `apt-get upgrade'. In the begin it
seemed as a usual upgrade but after a while (supposedly after these two
p
5 matches
Mail list logo
