gpg-agent cannot get started due to relocation error

Bug #1775783 reported by HongxuChen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnupg2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Running `gpg' related commands continues reporting:

gpg: can't connect to the agent: IPC connect call failed
gpg: error getting the KEK: No agent running

And results of `gpg-agent --daemon':

gpg-agent: relocation error: gpg-agent: symbol gcry_get_config version GCRYPT_1.6 not defined in file libgcrypt.so.20 with link time reference

Relevant packages that I have installed:
libgcrypt11:amd64 libgcrypt11-dev libgcrypt20:amd64 libgcrypt20-dev libgcrypt20:i386

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gpg-agent 2.2.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: LXQt
Date: Fri Jun 8 15:51:38 2018
InstallationDate: Installed on 2016-03-04 (825 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: gnupg2
UpgradeStatus: Upgraded to bionic on 2018-05-13 (25 days ago)

Revision history for this message
HongxuChen (hsxuif) wrote :
Revision history for this message
Aleksander Machniak (al3c) wrote :

Works for me, but....

I hit the same issue after upgrade and it was caused by another version (2.1.15) of gnupg installed from source on my system. After cleaning /usr/local from that version files it started working. So, maybe that's also the case for you.

Revision history for this message
HongxuChen (hsxuif) wrote :

Not my case. I haven't built any gnupg before and from results of `locate gnupg` and `find -name "*gnupg*"` there seem no relevant files. Indeed this issue occurred after I upgraded from 16.04 to 18.04.

Revision history for this message
HongxuChen (hsxuif) wrote :

Okay, I finally realized that it was my self-built libgcrypt that causes the issue.

Changed in gnupg2 (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.