Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apt upgrade stuck at "Setting up libc6:amd64 (2.37-14) ..." #11092

Closed
1 of 2 tasks
liyafe1997 opened this issue Jan 29, 2024 · 1 comment
Closed
1 of 2 tasks

apt upgrade stuck at "Setting up libc6:amd64 (2.37-14) ..." #11092

liyafe1997 opened this issue Jan 29, 2024 · 1 comment

Comments

@liyafe1997
Copy link

Windows Version

10.0.22631.3085

WSL Version

2.0.15.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.133.1-1

Distro Version

Debian testing

Other Software

No response

Repro Steps

In Debian Testing

sudo apt update
sudo apt dist-upgrade

While upgrading libc6:amd64 (2.37-14), it stuck forever.

Expected Behavior

Should be able to upgrade

Actual Behavior

screenshot

And I can see telinit u takes 100% CPU

A lot of people also having this problem:
https://stackoverflow.com/questions/77885938/stuck-setting-up-libc6i386

https://unix.stackexchange.com/questions/767340/apt-stuck-on-setting-up-libc6

Diagnostic Logs

No response

@cotste
Copy link

cotste commented Jan 30, 2024

I had the same issue, #11035 (comment) fixed it.

As far as I can tell if you don't have

[boot] systemd=true

The /run/systemd/system directory is not created and the tests in the postinst for libc fail:

    # Restart init.  Currently handles chroots, systemd and upstart, and
    # assumes anything else is going to not fail at behaving like
    # sysvinit:
    TELINIT=yes
    if ischroot 2>/dev/null; then
        # Don't bother trying to re-exec init from a chroot:
        TELINIT=no
    elif [ -n "${DPKG_ROOT:-}" ]; then
        # Do not re-exec init if we are operating on a chroot from outside:
        TELINIT=no
    elif [ -d /run/systemd/system ]; then
        # Restart systemd on upgrade, but carefully.
        # The restart is wanted because of LP: #1942276 and Bug: #993821
        # The care is needed because of https://bugs.debian.org/753725
        # (if systemd --help fails the system might still be quite broken but
        # that seems better than the kernel panic that results if systemd
        # cannot reexec itself).
        TELINIT=no
        if systemd --help >/dev/null 2>/dev/null; then
            systemctl daemon-reexec
        else
            echo "Error: Could not restart systemd, systemd binary not working" >&2
        fi
    fi
    if [ "$TELINIT" = "yes" ]; then
        telinit u 2>/dev/null || true ; sleep 1
    fi

@ghost ghost locked and limited conversation to collaborators Jan 30, 2024
@ghost ghost converted this issue into discussion #11097 Jan 30, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants