You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
elseecho"Error: Could not restart systemd, systemd binary not working">&2fifiif [ "$TELINIT"="yes" ];then
telinit u 2>/dev/null ||true; sleep 1
fi
ghost
locked and limited conversation to collaborators
Jan 30, 2024
Windows Version
10.0.22631.3085
WSL Version
2.0.15.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
Debian testing
Other Software
No response
Repro Steps
In Debian Testing
While upgrading
libc6:amd64 (2.37-14)
, it stuck forever.Expected Behavior
Should be able to upgrade
Actual Behavior
And I can see
telinit u
takes 100% CPUA 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
The text was updated successfully, but these errors were encountered: