/usr/lib/libc.so.6: version `GLIBC_2.34' not found

logart · 4 March 2022 14:40

I have run through a number of posts and tried a lot of commands and everything just pretty much fails like this:

pacman-key --init
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
chmod: cannot access '/etc/pacman.d/gnupg//trustdb.gpg': No such file or directory
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
==> Generating pacman master key. This may take some time.
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
==> Updating trust database...
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
==> ERROR: Trust database could not be updated.

logart · 4 March 2022 14:42

I am at a state now where most commands I try fail because of the glibc issue so I am concerned that hard-boot will end up with a failed OS. Hoping there is something I can do in this current state that can mitigate this.

Mirdarthos · 4 March 2022 14:43

Try:

pamac upgrade

See what happens.

logart · 4 March 2022 14:44

pamac upgrade
pamac: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by pamac)
pamac: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libxml2.so.2)
pamac: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
pamac: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libstdc++.so.6)
pamac: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libgcc_s.so.1)

Mirdarthos · 4 March 2022 14:46

Tip:

To provide terminal output, copy the text you wish to share, and paste it here, surrounded by three (3) backticks, a.k.a grave accents. Like this:

```
pasted text
```

This will just cause it to be rendered like this:

Portaest sed
elementum
cursus nisl nisi
hendrerit ac quis
sit
adipiscing
tortor sit leo commodo.

Instead of like this:

Portaest sed elementum cursus nisl nisi hendrerit ac quis sit adipiscing tortor sit leo commodo.

Thereby improving legibility and making it much easier for those trying to be of assistance. Please edit your post accordingly.

Edit:

Try:

pacman -S glibc lib32-glibc

logart · 4 March 2022 14:51

pacman -S glibc lib32-glibc
resolving dependencies...
looking for conflicting packages...

Packages (2) glibc-2.35-2  lib32-glibc-2.35-2

Total Installed Size:  66.98 MiB
Net Upgrade Size:       2.61 MiB

:: Proceed with installation? [Y/n] y
(2/2) checking keys in keyring                                                                [#######################################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
(2/2) checking package integrity                                                              [#######################################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
error: glibc: missing required signature
:: File /var/cache/pacman/pkg/glibc-2.35-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: lib32-glibc: missing required signature
:: File /var/cache/pacman/pkg/lib32-glibc-2.35-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

Mirdarthos · 4 March 2022 14:53

Well, I don’t like this, I don’t like it at all, but since there was a permission denied error previously, try:

sudo pacman-key --init

Edit:

Followed by, if successful:

sudo pacman -S glibc lib32-glibc

logart · 4 March 2022 14:54

sudo pacman-key --init
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
chmod: cannot access '/etc/pacman.d/gnupg//trustdb.gpg': No such file or directory
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
==> Generating pacman master key. This may take some time.
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
==> Updating trust database...
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
==> ERROR: Trust database could not be updated.
[stephen-x570gamingx logart]# ls -l /etc/pacman.d/gnupg/
total 8
-rw-r--r-- 1 root root  17 Mar  4 06:12 gpg-agent.conf
-rw-r--r-- 1 root root 105 Mar  4 06:12 gpg.conf
-rw-r--r-- 1 root root   0 Mar  4 06:12 pubring.gpg
-rw------- 1 root root   0 Mar  4 06:12 secring.gpg

Mirdarthos · 4 March 2022 14:56

logart · 4 March 2022 15:01

No success. I see the /etc/pacman.d/gnupg/ folder is missing some content.

ishaan2479 · 4 March 2022 15:05

@logart Follow the steps in the given tutorial. Looks like you didn’t update your system in a long time. It’s not given there but I hope you know that you have to execute all the commands with sudo which are specified there.

Mirdarthos · 4 March 2022 15:06

Well, according to:

logart · 4 March 2022 15:10

sudo pacman-key --init
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
chmod: cannot access '/etc/pacman.d/gnupg//trustdb.gpg': No such file or directory
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
==> Generating pacman master key. This may take some time.
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
==> Updating trust database...
gpg: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libsqlite3.so.0)
==> ERROR: Trust database could not be updated.

logart · 4 March 2022 15:10

sudo pacman -Syy gnupg archlinux-keyring manjaro-keyring
:: Synchronizing package databases...
 core                                                             169.1 KiB   355 KiB/s 00:00 [#######################################################] 100%
 extra                                                           1880.2 KiB   463 KiB/s 00:04 [#######################################################] 100%
 community                                                          6.9 MiB   628 KiB/s 00:11 [#######################################################] 100%
 multilib                                                         174.1 KiB   567 KiB/s 00:00 [#######################################################] 100%
warning: gnupg-2.2.32-2 is up to date -- reinstalling
warning: archlinux-keyring-20220224-1 is up to date -- reinstalling
warning: manjaro-keyring-20210910-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (3) archlinux-keyring-20220224-1  gnupg-2.2.32-2  manjaro-keyring-20210910-2

Total Download Size:    3.53 MiB
Total Installed Size:  11.57 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 gnupg-2.2.32-2-x86_64                                              2.4 MiB   806 KiB/s 00:03 [#######################################################] 100%
 archlinux-keyring-20220224-1-any                                1040.1 KiB  1238 KiB/s 00:01 [#######################################################] 100%
 manjaro-keyring-20210910-2-any                                   141.6 KiB   920 KiB/s 00:00 [#######################################################] 100%
 Total (3/3)                                                        3.5 MiB   851 KiB/s 00:04 [#######################################################] 100%
(3/3) checking keys in keyring                                                                [#######################################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
(3/3) checking package integrity                                                              [#######################################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
error: gnupg: missing required signature
:: File /var/cache/pacman/pkg/gnupg-2.2.32-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: archlinux-keyring: missing required signature
:: File /var/cache/pacman/pkg/archlinux-keyring-20220224-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: manjaro-keyring: missing required signature
:: File /var/cache/pacman/pkg/manjaro-keyring-20210910-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

Mirdarthos · 4 March 2022 15:21

Only other thing I can recommend, and I’m not even sure this’d work, is trying it from within a chroot environment. But somehow I don’t think it’d work…

I don’t have an idea further, as that file, libc.so.6 can’t be found, or something…

logart · 4 March 2022 15:25

It is there, but linked to the wrong version.

ls -l /usr/lib/libc.so.6
lrwxrwxrwx 1 root root 12 May 12  2021 /usr/lib/libc.so.6 -> libc-2.33.so

Mirdarthos · 4 March 2022 15:26

Try:

sudo pacman-key --refresh-keys

See if that helps.

logart · 4 March 2022 15:28

sudo pacman-key --verbose --refresh-keys                                                                                           ✔  3.0.0  
==> ERROR: You do not have sufficient permissions to read the pacman keyring.
==> Use 'pacman-key --init' to correct the keyring permissions.
    ~          
```                                               `

ishaan2479 · 4 March 2022 15:31

Okay so will not bother in this thread again but here you had to enter yes in all the steps.

Mirdarthos · 4 March 2022 15:33

logart:

sudo pacman-key --verbose --refresh-keys                                                                                           ✔  3.0.0  
==> ERROR: You do not have sufficient permissions to read the pacman keyring.
==> Use 'pacman-key --init' to correct the keyring permissions.
    ~          
```                                               `

OK, seeing as you cannot even do it with sudo, see if you can change to root and then do it:

Run,

su -

to change to root. If successful, run the following again:

sudo pacman-key --verbose --refresh-keys

Edit:

If you get an error again, still in the root environment, run:

pacman-key --init

And retry.