[SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

vlsd · 2014-01-13 18:00:19

I was away from my machine for a while and did a system upgrade this morning. A lot of packages, like I'd expect and then halfway through I started getting messages about libgcrypt and invalid GPG engines. Anyway, long story short, my system is crippled due to everything being up to date except libgcrypt which is version 1.5.3-1 and pacman refuses to update it due to GPG errors (go figure).

The deets are as follows:

When I try and run a bunch of commands on my computer, I get a libgcrypt error such as this one:

# sudo halt
halt: error while loading shared libraries: libgcrypt.so.20: cannot open shared object file: No such file or directory

When I try to (forcefully) upgrade libgcrypt, I get the following:

#  sudo pacman -S --force libgcrypt                                                                                                                         1 
resolving dependencies...
looking for inter-conflicts...

Packages (1): libgcrypt-1.6.0-1

Total Installed Size:   1.09 MiB
Net Upgrade Size:       0.38 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                  [########################################################] 100%
error: GPGME error: Invalid crypto engine
(1/1) checking package integrity                                                                [########################################################] 100%
error: GPGME error: Invalid crypto engine
error: libgcrypt: missing required signature
:: File /var/cache/pacman/pkg/libgcrypt-1.6.0-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

So, I'm not sure what's going on here, but it seems to me that libgcrypt needs to be upgraded for pacman to upgrade libgcrypt. Can someone please help?

Last edited by vlsd (2014-01-13 19:09:19)

Scimmia · 2014-01-13 18:06:42

If you're sure the package you downloaded is good, I would try simply disabling sig checking in pacman.conf, SigLevel=Never. Don't forget to change it back after you upgrade libgcrypt.

Last edited by Scimmia (2014-01-13 18:07:20)

mcloaked · 2014-01-13 18:34:42

Scimmia wrote:

If you're sure the package you downloaded is good, I would try simply disabling sig checking in pacman.conf, SigLevel=Never. Don't forget to change it back after you upgrade libgcrypt.

Yes this works - though is this now also related to the kernel not booting after updating before libgcrypt was updated? Or is that a separate issue?

Last edited by mcloaked (2014-01-13 18:34:58)

Scimmia · 2014-01-13 18:36:20

It could be, you said the error was something about encryption.

vlsd · 2014-01-13 19:09:01

Scimmia wrote:

If you're sure the package you downloaded is good, I would try simply disabling sig checking in pacman.conf, SigLevel=Never. Don't forget to change it back after you upgrade libgcrypt.

This fixed my problem. Thank you!

vlsd · 2014-01-13 19:10:34

mcloaked wrote:

Scimmia wrote:
If you're sure the package you downloaded is good, I would try simply disabling sig checking in pacman.conf, SigLevel=Never. Don't forget to change it back after you upgrade libgcrypt.
Yes this works - though is this now also related to the kernel not booting after updating before libgcrypt was updated? Or is that a separate issue?

Should I be worried about booting my new kernel after the update?

Maty · 2014-01-13 19:22:34

I had the same problem and so I chrooted into my system with Arch USB media, disabled the signature check in pacman (SigLevel = Never in /etc/pacman.conf), run pacman -Syu and finally pacman-key --init. This seems to solve the problem for most of the people.

For me, my dm-crypt+LUKS encrypted root partition was still unable to be mounted correctly, but that was fixed with a basic mkinitcpio -p linux.

P.S. Special thanks to jordicoma and luigi at #archlinux for helping out with this!

Last edited by Maty (2014-01-13 19:25:38)

Scimmia · 2014-01-13 19:33:06

If you're going to boot from an install disk/USB anyway, "pacman --root <mountpoint> -Syu" would be preferred since that doesn't skip the signature check.

speedyx · 2014-01-13 20:06:13

Thank you all very much for this thread!

mcloaked · 2014-01-13 20:33:40

vlsd wrote:

mcloaked wrote:
Scimmia wrote:
If you're sure the package you downloaded is good, I would try simply disabling sig checking in pacman.conf, SigLevel=Never. Don't forget to change it back after you upgrade libgcrypt.
Yes this works - though is this now also related to the kernel not booting after updating before libgcrypt was updated? Or is that a separate issue?
Should I be worried about booting my new kernel after the update?

See my post at https://bbs.archlinux.org/viewtopic.php … 4#p1370454

EvanPurkhiser · 2014-01-13 20:33:50

Thanks for this. It looks like my mirror was out of sync and libgrcypt 1.5.3 was only available in core (as mentioned here). I had to grab 1.6 from the testing repository.

Also, another side note: For anyone still running systemd 204 or 205 (for systemd --user reasons) you will need to keep the /usr/lib/libgcrypt.so.11 blob since it seems to depend on it. Just another little push towards the edge for getting systemd --user 208 working the way I want.

JohnDVD · 2014-01-16 18:54:55

Thanks for this hint. But I had an additional problem.
I'm using xorg-server-1.11.4-2, which requires libgcrypt version < 1.6. It's because I've installed catalyst-total-hd234k (legacy ati/amd drivers).

The solution is to manually grab a copy of e.g. /usr/lib/libgcrypt.so.11.8.2 before updating libgcrypt.
Afterwards move saved libgcrypt.so.11.8.2 to /usr/lib/ and create a symbolic link to it named libgcrypt.so.11
Xorg111 is running well again.

JD

Scimmia · 2014-01-17 05:21:59

Untracked files in /usr/lib is not the answer, rebuilding the version of xorg you need against the new library is.

A wrong solution, but less wrong than what you're doing, is to use the libgcrypt15 package in the AUR.

EvanPurkhiser · 2014-01-17 08:09:55

@Scimmia: Thank you for that. You're right, rebuilding against the new library is a much better solution!

JohnDVD · 2014-01-17 15:28:52

@Scimmia
I knew it was a dirty fix. Thanks for your advice.
Maybe I'll rebuild xorg111 by myself later. I have no experiences in compiling against something.

Arch Linux

#1 2014-01-13 18:00:19

[SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#2 2014-01-13 18:06:42

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#3 2014-01-13 18:34:42

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#4 2014-01-13 18:36:20

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#5 2014-01-13 19:09:01

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#6 2014-01-13 19:10:34

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#7 2014-01-13 19:22:34

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#8 2014-01-13 19:33:06

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#9 2014-01-13 20:06:13

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#10 2014-01-13 20:33:40

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#11 2014-01-13 20:33:50

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#12 2014-01-16 18:54:55

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#13 2014-01-17 05:21:59

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#14 2014-01-17 08:09:55

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

#15 2014-01-17 15:28:52

Re: [SOLVED] Updating libgcrypt to libgcrypt 1.6.0-1 fails

Board footer