Re: libcrypt1: symlink points to libpthread
On 2021-09-30 15:46, shichimohedron wrote:
> >Can you please try to call /usr/sbin/ldconfig.old to check if the wrong
> link is recreated? That's needed to confirm if ldconfig is the culprit
> here.
> >Can you confirm it's libpthread.so.1 and not libpthread.so.0? If so can
> you please tell how did you install that file?
>
> Here is a shell log, literally
>
> ~# ls -l /lib/x86_64-linux-gnu/ | grep libcrypt
> -rw-r--r-- 1 root root 266262 Apr 18 20:46 libcrypt.a
> lrwxrwxrwx 1 root root 35 Apr 18 20:46 libcrypt.so -> /lib/x86_64-linux-gnu/libcrypt.so.1
> lrwxrwxrwx 1 root root 17 Apr 18 20:46 libcrypt.so.1 -> libcrypt.so.1.1.0
> -rw-r--r-- 1 root root 202680 Apr 18 20:46 libcrypt.so.1.1.0
> ~# /usr/sbin/ldconfig.old
> ~# ls -l /lib/x86_64-linux-gnu/ | grep libcrypt
> -rw-r--r-- 1 root root 266262 Apr 18 20:46 libcrypt.a
> lrwxrwxrwx 1 root root 35 Apr 18 20:46 libcrypt.so -> /lib/x86_64-linux-gnu/libcrypt.so.1
> lrwxrwxrwx 1 root root 15 Sep 30 07:53 libcrypt.so.1 -> libpthread.so.1
> -rw-r--r-- 1 root root 202680 Apr 18 20:46 libcrypt.so.1.1.0
Thanks for this log, it confirms that the wrong link is created by
ldconfig.
> I struggle to reveal the origins of libpthread.so.1. It can easily be a result of unqualified experimentation, but not necessarily. Of course, if this is the case its presence in the system is completely my fault and not in any sense yours. Anyway, dpkg -S doesn't match it with any of packages currently installed, and another attempts to guess where the library comes from didn't lead to any answer.
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
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: