Package: libcrypt1 Version: 1:4.4.18-4 Severity: grave Justification: renders package unusable X-Debbugs-Cc: shichimohed...@protonmail.com
Dear Maintainer, Recently I have upgraded from Buster to Bullseye and, among other things, have installed libcrypt1 package. Curiuosly enough, I found out that the symlink that should have been pointing to crypto library (/lib/x86_64-linux-gnu/libcrypto.so.1 -> libcrypto.so.1.1.0) pointed to libpthread.so.1 instead since upgrade. Consequently, no binary linked to libcrypt was able to load; specifically, /sbin/sulogin crashed with "/lib/x86_64-linux-gnu/libcrypto.so.1: version `XCRYPT_2.0' not found", and so /bin/login service was unable to operate, and I basically could not log into my system. I managed to find a way around the issue by deleting the symlink by hands and re-linking it properly, but I guess that a stable distribution should not behave like that. When I run apt-get reinstall libcrypt1 the link changes to libpthread.so.1 again, so it is clearly this package that causes trouble. As for now (09/29/2021 2:30 PM GMT) the bug keeps reappearing. -- System Information: Debian Release: 11.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU threads) Locale: LANG=C, LC_CTYPE=C.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 libcrypt1 depends on: ii libc6 2.31-13 libcrypt1 recommends no packages. libcrypt1 suggests no packages. -- no debconf information
