The presence of pinentry-qt4 breaks gnupg-agent

Bug #1509699 reported by Tony Houghton on 2015-10-24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnupg2 (Ubuntu)
Nominated for Wily by Alberto Salvia Novella
pinentry (Ubuntu)
Nominated for Wily by Alberto Salvia Novella

Bug Description

After upgrading to wily I found gnupg-agent had stopped working. Running it in a terminal revealed this error:

can't connect to the PIN entry module: End of file

Simply uninstalling the pinentry-qt4 binary package restored gnupg-agent's functionality.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: pinentry-qt4 (not installed)
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 24 19:40:23 2015
InstallationDate: Installed on 2014-06-13 (497 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: pinentry
UpgradeStatus: Upgraded to wily on 2015-10-24 (0 days ago)

Tony Houghton (h-realh) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pinentry (Ubuntu):
status: New → Confirmed
Changed in gnupg2 (Ubuntu):
status: New → Invalid
importance: Undecided → Critical
Changed in pinentry (Ubuntu):
importance: Undecided → Critical

This bug needs to be reported to the GnuPG bug tracker, but seems not to be working right now.

If I visit the bug tracker at (, the Chromium Web Browser says:

Your connection is not private

Attackers might be trying to steal your information from (for example, passwords, messages or credit cards). NET::ERR_CERT_COMMON_NAME_INVALID

I have reported it to the webmaster. If you see the link working properly again, please report there. Thanks.

Changed in pinentry (Ubuntu):
status: Confirmed → Triaged
Magnus Holmgren (holmgren) wrote :

I've encountered a bug that might be the same as this. Apparently pinentry-qt can't connect to the display. Adding keep-display to ~/.gnupg/gpg-agent.conf is a workaround.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers