Arch Linux

neeasade

Member

Registered: 2014-03-30

Posts: 3

[solved] error: GPGME error: Invalid crypto engine

Whenever I try to install a package or -Syu, I get GPGME error, invalid crypto engine, followed by an error about corrupted package or PGP signature.

Googling led me to find that others have had this problem before, but the documented solutions are not working for me.

I cannot pacman -S <package> without something like the log below happening.

I have tried:
- Mounting from liveCD, pacman -Syu --root /mnt (which worked for upgrading packages, but the problem remains)
- disabling package signing, pacman -Syu, re-enable package signing
- Refreshing the keyring
- $ pacman-key --init
- Remove /etc/pacman.d/gnupg, pacman-key --init && pacman-key --populate archlinux
- sanity check: I have these packages in my system: gnupg gpgme libgcrypt
- sanity check: btrfs scrub shows disk status to be okay, no missing checksums/drive health errors afaik.

One solution cited was to downgrade the linux kernel, sync libgcrypt, then sync the kernel - I cannot downgrade the kernel as it is not in my cache, and I don't believe that would be an issue anymore since I was able to -Syu from live cd past that.

related posts:
https://bbs.archlinux.org/viewtopic.php … 4#p1370454
https://bbs.archlinux.org/viewtopic.php?id=203400

sudo pacman -Syu
[sudo] password for neeasade: 
:: Synchronizing package databases...
 core                                                           122.1 KiB   223K/s 00:01 [####################################################] 100%
 extra                                                         1803.0 KiB   855K/s 00:02 [####################################################] 100%
 community                                                        3.1 MiB   340K/s 00:09 [####################################################] 100%
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (10) cryptsetup-1.7.0-1  device-mapper-2.02.133-1  libevdev-1.4.5-1  libtirpc-1.0.1-2  lvm2-2.02.133-1  man-db-2.7.5-1  mesa-11.0.5-1
              mesa-libgl-11.0.5-1  pam-1.2.1-2  xf86-input-synaptics-1.8.3-1

Total Download Size:    9.68 MiB
Total Installed Size:  45.84 MiB
Net Upgrade Size:       0.91 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages ...
 libtirpc-1.0.1-2-x86_64                                        171.5 KiB  70.7K/s 00:02 [####################################################]   1%
 pam-1.2.1-2-x86_64                                             779.6 KiB  83.4K/s 00:09 [####################################################]   7%
 device-mapper-2.02.133-1-x86_64                               1042.8 KiB  90.0K/s 00:12 [####################################################]  10%
 cryptsetup-1.7.0-1-x86_64                                     1266.6 KiB  87.5K/s 00:14 [####################################################]  12%
 lvm2-2.02.133-1-x86_64                                           2.2 MiB   106K/s 00:21 [####################################################]  22%
 man-db-2.7.5-1-x86_64                                            2.6 MiB   114K/s 00:23 [####################################################]  26%
 libevdev-1.4.5-1-x86_64                                          2.6 MiB   113K/s 00:24 [####################################################]  27%
 mesa-11.0.5-1-x86_64                                             9.6 MiB   188K/s 00:52 [####################################################]  99%
 mesa-libgl-11.0.5-1-x86_64                                       9.6 MiB   188K/s 00:52 [####################################################]  99%
 xf86-input-synaptics-1.8.3-1-x86_64                              9.7 MiB   188K/s 00:53 [####################################################] 100%
(10/10) checking keys in keyring                                                         [####################################################] 100%
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
(10/10) checking package integrity                                                       [####################################################] 100%
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: GPGME error: Invalid crypto engine
error: libtirpc: missing required signature
:: File /var/cache/pacman/pkg/libtirpc-1.0.1-2-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 

Last edited by neeasade (2015-11-11 17:56:07)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,559

Re: [solved] error: GPGME error: Invalid crypto engine

First thing I would try is reinstalling the gpgme package and it's dependencies. You should be able to do this from the cache.

Last edited by Scimmia (2015-11-11 17:41:46)

neeasade

Member

Registered: 2014-03-30

Posts: 3

Re: [solved] error: GPGME error: Invalid crypto engine

Okay, so I pacman -S libgpg-error gnupg gpgme, and found a bunch of gnupg files existing in filesystem, and thus couldn't continue. what I did then was sync them with a --force. then I had an invalid /etc/pacman.d/gnupg/trustdb (possibly from my prev attempts to reset this) - removing the gnupg dir after that, followed by a pacman-key init and a pacman-key --populate  archlinux did the trick. Thank you.

Perhaps my problem was I stopped an upgrade mid-migration for gnupg for some reason/accident.

I also recognize your name from some prev related posts on this. Thanks.