Package: iputils-ping Version: 3:20200821-2 Severity: normal X-Debbugs-Cc: witold.bary...@gmail.com
I noticed this weird thing: 1) ping is working 2) start apt dist-upgrade 3) at some point new ping stops working with ping: socket: Operation not permited for minutes. 4) apt dist-upgrade finishes 5) ping works again That is not nice. Looking at dpkg.log I see this: 2020-09-24 01:34:40 upgrade iputils-ping:amd64 3:20190709-3 3:20200821-2 2020-09-24 01:34:40 status half-configured iputils-ping:amd64 3:20190709-3 2020-09-24 01:34:40 status unpacked iputils-ping:amd64 3:20190709-3 2020-09-24 01:34:40 status half-installed iputils-ping:amd64 3:20190709-3 2020-09-24 01:34:40 status unpacked iputils-ping:amd64 3:20200821-2 ... ... 2020-09-24 01:45:28 configure iputils-ping:amd64 3:20200821-2 <none> 2020-09-24 01:45:28 status unpacked iputils-ping:amd64 3:20200821-2 2020-09-24 01:45:28 status half-configured iputils-ping:amd64 3:20200821-2 2020-09-24 01:45:28 status installed iputils-ping:amd64 3:20200821-2 So I suspect there is something critical in configure that prevent ping from working during this intermitent period. Wish it could be fixed somehow. -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/32 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages iputils-ping depends on: ii libc6 2.31-3 ii libcap2 1:2.43-1 ii libcap2-bin 1:2.43-1 ii libidn2-0 2.3.0-1 iputils-ping recommends no packages. iputils-ping suggests no packages. -- no debconf information
