Your message dated Thu, 30 Sep 2021 18:34:35 +0200
with message-id <YVXnG26PqpL0d5/v...@bongo.bofh.it>
and subject line Re: libcrypt1: symlink points to libpthread
has caused the Debian Bug report #995308,
regarding libcrypt1: symlink points to libpthread
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
995308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Thank you Aurelien for your help, so this is user error.
On Sep 30, shichimohedron <shichimohed...@protonmail.com> wrote:
>
> On Thursday, September 30th, 2021 at 12:08 PM, Aurelien Jarno
> <aurel...@aurel32.net> wrote:
>
> > It could be that this libpthread.so.1 file is actually a copy of an old
> >
> > libcrypt.so.1. It's something you can check with:
> >
> > readelf --dynamic /lib/x86_64-linux-gnu/libpthread.so.1 | grep SONAME
>
> And it actually is:
>
> ~# readelf --dynamic /lib/x86_64-linux-gnu/libpthread.so.1 | grep SONAME
> 0x000000000000000e (SONAME) Library soname: [libcrypt.so.1]
--
ciao,
Marco
signature.asc
Description: PGP signature
--- End Message ---
