Bug#1057783: libc6:amd64.postinst may lack of response for a long time.

[ChenPi11]

Package: libc6
Version: 2.37-13
Severity: normal
Tags: d-i
X-Debbugs-Cc: wushengwuxi...@outlook.com

Dear Maintainer,

When apt was configuring the libc6:amd64 after I upgraded all packages, It lack of response for a long time (more than 3 hours).
Then, I founded that `ischroot` program was blocking the post-install
script. I think the bug is ischroot's at first. But it ONLY unresponsive here.
I know the apt is not in chroot, so I removed the command and set
`TELINIT` to `no`. After I did this, the configure process became
normaly.


-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.133.1-microsoft-standard-WSL2 (SMP w/8 CPU threads)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages libc6 depends on:
ii libgcc-s1 13.2.0-8

Versions of packages libc6 recommends:
ii libidn2-0 2.3.4-1+b1

Versions of packages libc6 suggests:
ii debconf [debconf-2.0] 1.5.82
pn glibc-doc <none>
ii libc-l10n 2.37-13
pn libnss-nis <none>
pn libnss-nisplus <none>
ii locales 2.37-13

-- debconf information:
glibc/kernel-not-supported:
glibc/restart-failed:
glibc/kernel-too-old:
glibc/upgrade: true
libraries/restart-without-asking: false
glibc/disable-screensaver:
glibc/restart-services:

[Aurelien Jarno]

Hi,

On 2023-12-08 21:04, ChenPi11 wrote:
> Package: libc6
> Version: 2.37-13
> Severity: normal
> Tags: d-i
> X-Debbugs-Cc: wushengwuxi...@outlook.com
>
> Dear Maintainer,
>
> When apt was configuring the libc6:amd64 after I upgraded all packages, It lack of response for a long time (more than 3 hours).
> Then, I founded that `ischroot` program was blocking the post-install
> script. I think the bug is ischroot's at first. But it ONLY unresponsive here.
> I know the apt is not in chroot, so I removed the command and set
> `TELINIT` to `no`. After I did this, the configure process became
> normaly.

Thanks for the report. It happens that the call to ischroot is essential
to not break the system when executing in a chroot. Therefore we have to
understand why ischroot is hanging.

As the problem is not reproducible here, could you please use strace
with the -p option on the hanging ischroot process to get a better idea
why it hangs?

Regards,
Aurelien

--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aure...@aurel32.net http://aurel32.net

[Hae-woo Park]

FYI, I experienced the same issue in my WSL systems in two different laptops running Trixie.

I am afraid if this would happen for other people's WSL systems.