apt-get update && apt-get upgrade trouble

[sweeder]

This is bug tracker is monitored by Windows Subsystem for Linux development team and other technical folks.

Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to GitHub issues.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".
You can find instructions to do that here: https://support.microsoft.com/en-us/help/315263/how-to-read-the-small-memory-dump-file-that-is-created-by-windows-if-a

If this is a console issue (a problem with layout, rendering, colors, etc.), please post the issue to the Terminal tracker: https://github.com/microsoft/terminal/issues
For documentation improvements, please post to the documentation tracker: https://github.com/MicrosoftDocs/WSL/issues
For any other questions on contributing please see our contribution guidelines: https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md

Please fill out the items below.
-->

# Environment

Windows build number: [ Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0]
Your Distribution version: [Ubuntu lsb_release 20.04 & 18.04, Debian, & Kali Linux]
Whether the issue is on WSL 2 and/or WSL 1: [WSL 2]

**# Steps to reproduce**

<!--  What you're doing and what's happening. Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screenshots if that helps demonstrate the problem. -->
Every (sudo apt update && sudo apt upgrade -y) command I input I get an output of:

Aborted (core dumped)
ldconfig: Can't stat /usr/local/lib/x86_64-linux-gnu: No such file or directory
ldconfig: Path `/usr/lib/x86_64-linux-gnu' given more than once
ldconfig: Path `/lib/x86_64-linux-gnu' given more than once
ldconfig: Path `/usr/lib/x86_64-linux-gnu' given more than once
ldconfig: Path `/usr/lib' given more than once
/usr/local/lib:
/lib/x86_64-linux-gnu:
Aborted (core dumped)
dpkg: error processing package libc-bin (--configure):
 installed libc-bin package post-installation script subprocess returned error exit status 134
Errors were encountered while processing:
 libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1) 

Error message I've been struggling with this for 3 weeks now, I'm tapped out
-->

**#  Expected behavior**

<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->
So like many Windows users, I'm excited to use Linux vm's without additional software. But after installing Debian, Ubuntu, & Kali Linux I can't get around a dpkg issue.

[therealkenc]

That dpkg error is from userspace (ie not WSL). No wild guesses how all your distros (Ubuntu,Debian,Kali) got in this state although it is possible if you did the same (unknown) thing on all three. There is an askubuntu here.

You can try whatever "fix broken libc" rain dances you find on the interwebs (serverfault etc) but if it were me I'd back up your 18.04 /home and re-install from the Store. For 20.04 and Kali heads up #4898. Conservative thing to do would be stick to 18.04.

[sweeder]

Thanks for your response man, I appreciate your input, I'll try reading the Ubuntu link before making my next move.

[sweeder]

Just sudo apt install libc-bin did the trick - problem solved. Thanks!

[sweeder]

Just sudo apt install libc-bin did the trick - problem solved. Thanks!

only worked for Ubuntu 18.04 though.

[sweeder]

Just sudo apt install libc-bin did the trick - problem solved. Thanks!

only worked for Ubuntu 18.04 though.

Same error message on Debian, Kali, and Ubuntu 20.04

[therealkenc]

only worked for Ubuntu 18.04 though.

Yeah 20.04 or any rolling distro is going to suffer #4898. Guidance would be (in order of sensibility) (a) stick to 18.04, (b) wait patiently for #4898 to backported, or, (c) try the work-arounds over there. With the caveat that it is possible to bork one's distro install without the help of WSL bugs. That link I gave you was just a random Google hit. There are a dozen other "fix my broken libc" rain dances you can try with varying degrees of success or failure.