Downgraded two packages, and I now I deeply regret

I downgraded two packages, as you do, and now system with Gnome is borked.
glibc-2.29-1 -> glibc-2.28-5
lib32-glibc-2.29-1 -> lib32-glibc-2.28-5
It still allows access to TTY and Manjaro chroot of a live USB.
So, when I try to update, I get this:

[manjaro-gnome /]# sudo pacman -S lib32-glibc
resolving dependencies...
looking for conflicting packages...

Packages (2) glibc-2.29-1  lib32-glibc-2.29-1

Total Installed Size:  62.29 MiB
Net Upgrade Size:      16.78 MiB

:: Proceed with installation? [Y/n] 
(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.29-1-x86_64.pkg.tar.xz 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.29-1-x86_64.pkg.tar.xz 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.

Helpfully, it suggest that I use pacman-key --init, but...

[manjaro-gnome /]# sudo pacman-key --init
gpg: /usr/lib/libm.so.6: version `GLIBC_2.29' 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/libm.so.6: version `GLIBC_2.29' not found (required by /usr/lib/libsqlite3.so.0)
gpg: /usr/lib/libm.so.6: version `GLIBC_2.29' not found (required by /usr/lib/libsqlite3.so.0)
==> Updating trust database...
gpg: /usr/lib/libm.so.6: version `GLIBC_2.29' not found (required by /usr/lib/libsqlite3.so.0)
==> ERROR: Trust database could not be updated.

I have tried with the advice Issues with “signature is marginal trust” or “invalid or corrupted package”, but the system still insists that packages are corrupted or invalid.

sudo pacman-mirrors -f5 && sudo pacman -Syyu

Not good.

Don't do

2 Likes

It happily creates a new mirror list, but when upgrading the Pacman still gives the same warnings as in my first post:

warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine

etc, etc...

Try:

sudo pacman -Sy archlinux-keyring && sudo pacman -Syyu

If no love, try:

sudo pacman-key --refresh-keys --keyserver pgp.mit.edu

2 Likes

Also look here

1 Like

Maybe this topic should be renamed as a warning to other users to "PSA - Downgrading glibc to 2.28-5 breaks GNOME desktop environment"

Partial downgrades can cause breakage just as partial upgrades can. Both should be avoided at all costs.

2 Likes

Just a thought, the packages are still in your cache?

sudo pacman -U /var/cache/pacman/pkg/glibc-2.29-1-x86_64.pkg.tar.xz

Does that throw errors?

Also why? I am intrigued :smiley:

4 Likes

May I know whichever wisdom on this earth, brought you to touch freaking glibc?

2 Likes

Restoring a backup doesn't work either??


:smiley:

5 Likes

This fixed it. Damn obvious in hindsight. I don't know how I missed that one.
I messed with downgrade because of some dependency.

1 Like

Because eveyone loves to watch a train wreck. :slight_smile:

3 Likes