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

When I try to run commands I see this:

ps -ef
ps: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libgcc_s.so.1)

I am unable to complete this package update process.

pacman -Syyu
:: Synchronizing package databases...
 core                                                             166.2 KiB   416 KiB/s 00:00 [#######################################################] 100%
 extra                                                           1889.5 KiB  9.37 MiB/s 00:00 [#######################################################] 100%
 community                                                          7.0 MiB  30.8 MiB/s 00:00 [#######################################################] 100%
 multilib                                                         174.0 KiB  3.62 MiB/s 00:00 [#######################################################] 100%
:: Starting full system upgrade...
warning: python-pyqt5: local (5.15.6-7.1) is newer than extra (5.15.6-7)
resolving dependencies...
looking for conflicting packages...

Packages (3) glibc-2.35-2  lib32-glibc-2.35-2  npm-8.5.1-1

Total Download Size:   13.44 MiB
Total Installed Size:  73.01 MiB
Net Upgrade Size:       2.63 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 glibc-2.35-2-x86_64                                                9.9 MiB  7.45 MiB/s 00:01 [#######################################################] 100%
 lib32-glibc-2.35-2-x86_64                                          3.5 MiB  4.92 MiB/s 00:01 [#######################################################] 100%
 Total (2/2)                                                       13.4 MiB  6.28 MiB/s 00:02 [#######################################################] 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: 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: npm: missing required signature
:: File /var/cache/pacman/pkg/npm-8.5.1-1-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.

Hi @logart,

Well, have you?

Also, please see [root tip] Mitigate and prevent GPGME error when syncing your system

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.

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.

Try:

pamac upgrade

See what happens.

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)

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
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.

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
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

:point_up_2:

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

@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.

Well, according to:

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.

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.

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…

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

Try:

sudo pacman-key --refresh-keys

See if that helps.

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.
    ~          
```                                               `