[SOLVED] Slackpkg returning slackware repository invalid gpg error

linux91 · 04-30-2021, 08:40 AM

Has anyone else seen this error?
Attempting to install some alienbob packages using slackpkg returned an invalid slackware repository error.
"Fatal: Slackware repository does not contains the official gpg-key!!
gpg: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory"

Slackware Current (15 beta)
slackpkg - version 15.0.2
Kernel 5.10.33 #1 SMP Wed Apr 28 12:55:31 CDT 2021 x86_64 Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz GenuineIntel GNU/Linux

crts · 04-30-2021, 09:07 AM

Quote:

Originally Posted by linux91

gpg: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory"

Is this a full install? Looks like 'gpg' cannot find a library (libudev.so.0) and fails.

What is the output of

Code:

# slackpkg file-search libudev

Petri Kaukasoina · 04-30-2021, 09:43 AM

libudev.so.0 was part of the old udev package. Nov 20 2015 Slackware moved from udev to eudev. Now it should be libudev.so.1. Maybe you have some old libraries which link to the old libudev.so.0 ?
Install-new, upgrade-all, clean-system, and remove old trash under /usr/local ?

linux91 · 04-30-2021, 09:45 AM

#crts, here is the result

**************************************************************
sudo /usr/sbin/slackpkg file-search libudev
Password:

FATAL! No Slackware GPG-KEY imported.
If you are upgrading from an older release of slackpkg+, all keys must to be reimported.
Please run
# slackpkg update gpg
**************************************************************
I started the updates with
slackpkg install-new (nothing new found)
slackpkg upgrade multilib (no upgrades available)
slackpkg upgrade alienbob (no upgrades of installed pkgs avail.)
Then I looked for new alienbob packages...
The error appeared in the middle of a 'slackpkg install alienbob'
Maybe the alienbob upgrade replaced a library?

linux91 · 04-30-2021, 09:48 AM

An attempt to update the gpg keys results in:

**************************************************************
sudo /usr/sbin/slackpkg update gpg

2021-04-30 10:37:49 URL:https://mirrors.slackware.com/slackw...urrent/GPG-KEY [1572/1572] -> "/tmp/slackpkg.draJrQ/gpgkey" [1]
gpg: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory
gpg: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

!!! F A T A L !!!
Slackware repository does NOT contain the Official GPG-KEY
You SHOULD disable GPG Strict check 'STRICTGPG=off'
in /etc/slackpkg/slackpkgplus.conf
**************************************************************

Petri Kaukasoina · 04-30-2021, 09:51 AM

The problem is your gpg does not work. Try 'gpg'. Try 'ldd /usr/bin/gpg'. (ldd should not show anything outside /lib64 and /usr/lib64. For example under /usr/local...)

linux91 · 04-30-2021, 09:54 AM

An excerpt of a search for libudev follows:

**************************************************************
sudo locate libudev
Password:
/boot/initrd-tree/lib/libudev.so.1
/boot/initrd-tree/lib/libudev.so.1.6.3
/boot/initrd-tree/lib64/libudev.so.1
/boot/initrd-tree/lib64/libudev.so.1.6.3
/lib/libudev.so.1
/lib/libudev.so.1.6.3
/lib64/libudev.so.1
/lib64/libudev.so.1.6.3
/usr/include/libudev.h
/usr/lib/libudev.so
/usr/lib/pkgconfig/libudev.pc
/usr/lib64/libudev.so
**************************************************************
I could try creating a soft link to the /lib* versions...

linux91 · 04-30-2021, 09:58 AM

#Petri, here are the results of your suggestions:

**************************************************************
sudo /usr/bin/gpg
Password:
/usr/bin/gpg: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

**************************************************************
sudo ldd /usr/bin/gpg
linux-vdso.so.1 (0x00007ffc00bed000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f7ad0062000)
libz.so.1 => /lib64/libz.so.1 (0x00007f7ad0048000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f7ad0035000)
libreadline.so.8 => /usr/lib64/libreadline.so.8 (0x00007f7acffde000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f7acffd9000)
libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007f7acffd2000)
libc.so.6 => /lib64/libc.so.6 (0x00007f7acfdf1000)
libtinfo.so.6 => /usr/lib64/libtinfo.so.6 (0x00007f7acfdc3000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7ad00ce000)
libusb-1.0.so.0 => /usr/lib64/libusb-1.0.so.0 (0x00007f7acfbad000)
libudev.so.0 => not found
librt.so.1 => /lib64/librt.so.1 (0x00007f7acfba3000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7acfb80000)
**************************************************************

Petri Kaukasoina · 04-30-2021, 10:05 AM

Do you get the same output as I do ? I mean the versions of aaa_libraries package and libusb. And the fact that there should not be aaa_elflibs.

Code:

$ (cd /var/adm/packages && ls -l aaa_* libusb-1*)
-rw-r--r-- 1 root root  2134 2021-02-15 22:56 aaa_base-14.2-x86_64-7
-rw-r--r-- 1 root root  8505 2021-04-02 10:26 aaa_glibc-solibs-2.33-x86_64-2
-rw-r--r-- 1 root root  5032 2021-04-20 08:02 aaa_libraries-15.0-x86_64-6
-rw-r--r-- 1 root root 14411 2021-02-15 22:56 aaa_terminfo-6.2_20201219-x86_64-4
-rw-r--r-- 1 root root   962 2021-04-17 09:50 libusb-1.0.24-x86_64-4
$ ls -l /usr/lib64/libusb-1.0.so*
lrwxrwxrwx 1 root root     19 2021-04-17 09:50 /usr/lib64/libusb-1.0.so -> libusb-1.0.so.0.3.0
lrwxrwxrwx 1 root root     19 2021-04-17 09:50 /usr/lib64/libusb-1.0.so.0 -> libusb-1.0.so.0.3.0
-rwxr-xr-x 1 root root 117848 2021-04-16 21:12 /usr/lib64/libusb-1.0.so.0.3.0

linux91 · 04-30-2021, 10:08 AM

This seems to correct the problem with gpg:

**************************************************************
cd /lib64
sudo ln -s libudev.so.1.6.3 libudev.so.0
**************************************************************

The results of ldd on gpg:
**************************************************************
sudo ldd /usr/bin/gpg
linux-vdso.so.1 (0x00007ffe52ad8000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f6647ab4000)
libz.so.1 => /lib64/libz.so.1 (0x00007f6647a9a000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f6647a87000)
libreadline.so.8 => /usr/lib64/libreadline.so.8 (0x00007f6647a30000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f6647a2b000)
libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007f6647a24000)
libc.so.6 => /lib64/libc.so.6 (0x00007f6647843000)
libtinfo.so.6 => /usr/lib64/libtinfo.so.6 (0x00007f6647815000)
/lib64/ld-linux-x86-64.so.2 (0x00007f6647b20000)
libusb-1.0.so.0 => /usr/lib64/libusb-1.0.so.0 (0x00007f66475ff000)
libudev.so.0 => /lib64/libudev.so.0 (0x00007f66475da000)
librt.so.1 => /lib64/librt.so.1 (0x00007f66475d0000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f66475af000)
**************************************************************

Testing gpg and the subsequent update:
**************************************************************
sudo /usr/bin/gpg (started successfully)
gpg: Go ahead and type your message ...
^C
gpg: signal 2 caught ... exiting

sudo /usr/sbin/slackpkg update gpg (updated successfully)
**************************************************************
Before I continue, are there any concerns about doing this workaround?

linux91 · 04-30-2021, 10:10 AM

Quote:

Originally Posted by Petri Kaukasoina

Do you get the same output as I do ? I mean the versions of aaa_libraries package and libusb. And the fact that there should not be aaa_elflibs.

Code:

$ (cd /var/adm/packages && ls -l aaa_* libusb-1*)
-rw-r--r-- 1 root root  2134 2021-02-15 22:56 aaa_base-14.2-x86_64-7
...
1.0.so.0 -> libusb-1.0.so.0.3.0
-rwxr-xr-x 1 root root 117848 2021-04-16 21:12 /usr/lib64/libusb-1.0.so.0.3.0

Let me check...

Petri Kaukasoina · 04-30-2021, 10:12 AM

I never link to a different library version but it's your system...

linux91 · 04-30-2021, 10:21 AM

Looks like aaa_elflibs and some extra alienbob versions of the libraries.
Also /usr/lib64/libusb-1.0.so is pointing to an older version of libusb-1.0.

**************************************************************
(cd /var/adm/packages && ls -l aaa_* libusb-1*)
-rw-r--r-- 1 root root 2134 Feb 16 13:50 aaa_base-14.2-x86_64-7
-rw-r--r-- 1 root root 3353 Jan 23 12:03 aaa_elflibs-15.0-x86_64-30
-rw-r--r-- 1 root root 3346 Jan 15 07:48 aaa_elflibs-compat32-15.0-x86_64-29compat32
-rw-r--r-- 1 root root 15496 Apr 4 12:02 aaa_glibc-solibs-2.33_multilib-x86_64-2alien
-rw-r--r-- 1 root root 5032 Apr 20 08:35 aaa_libraries-15.0-x86_64-6
-rw-r--r-- 1 root root 4931 Apr 24 09:05 aaa_libraries-compat32-15.0-x86_64-6compat32
-rw-r--r-- 1 root root 14411 Feb 16 13:50 aaa_terminfo-6.2_20201219-x86_64-4
-rw-r--r-- 1 root root 962 Apr 17 09:28 libusb-1.0.24-x86_64-4
**************************************************************

**************************************************************
ls -l /usr/lib64/libusb-1.0.so*
lrwxrwxrwx 1 root root 19 Apr 30 09:24 /usr/lib64/libusb-1.0.so -> libusb-1.0.so.0.1.0*
lrwxrwxrwx 1 root root 19 Apr 30 09:24 /usr/lib64/libusb-1.0.so.0 -> libusb-1.0.so.0.1.0*
-rwxr-xr-x 1 root root 90160 Sep 3 2013 /usr/lib64/libusb-1.0.so.0.1.0*
-rwxr-xr-x 1 root root 117848 Apr 16 14:12 /usr/lib64/libusb-1.0.so.0.3.0*
**************************************************************

linux91 · 04-30-2021, 10:23 AM

I probably missed an upgrade notice from alienbob that addressed this.

Petri Kaukasoina · 04-30-2021, 10:27 AM

You have forgotten to give slackpkg clean-system after beginning of February. You should get rid of aaa_elflibs and after that reinstall aaa_libraries. (And the same for the compat32 ones).

It's this:

Code:

+--------------------------+
Mon Feb  8 05:13:26 UTC 2021
a/aaa_elflibs-15.0-x86_64-30.txz:  Removed.
  Renamed to aaa_libraries.
...
a/aaa_libraries-15.0-x86_64-1.txz:  Added.
  This package has been renamed from aaa_elflibs to insure that it will come
  after aaa_glibc-solibs when upgraded in alphabetical order.