gnupg2 : pinentry cache is not clear : gpg-agent

Bug #1824969 reported by Michel Le Cocq on 2019-04-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnupg2 (Debian)
Fix Released
gnupg2 (Ubuntu)

Bug Description

I encounter the same bug as this Debian one : [Debian Bug report logs - #919856](

I've test gpg-agent with gnupg2 and pinentry with this several version and all have the same trouble :

Ubuntu 18.04.2 LTS Bionic Beaver
gnupg2 2.2.4-1

Ubuntu 18.10 Cosmic Cuttlefish
gnupg2 2.2.8-3

Ubuntu 19.04 LTS Disco Dingo
gnupg2 2.2.12-1

In fact it's a GnuPG bug see : [](

This bug is corrected in GnuPG 2.2.13-1.

Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Do you have steps that can be used to trigger the issue?

Changed in gnupg2 (Ubuntu):
importance: Undecided → High
status: New → Fix Committed
Michel Le Cocq (nomad-fr) wrote :

it's exactly the same procedure has describe in Debian bug.

In fact I configure a yubikey with a ssh key inside.

Whenever I try to connect somewhere, where I'm sure my pub key is I get:

 sign_and_send_pubkey: signing failed: agent refused operation

Michel Le Cocq (nomad-fr) wrote :

I just see the fix is committed, when will we see it ?

Sebastien Bacher (seb128) wrote :

It's commited upstream and in Debian so we will get it when next Ubuntu cycle start. Then we can look at doing a SRU but for that we need a testcase which can be used to verify the SRU (and ideally which doesn't require buying hardware like an yubikey)

Changed in gnupg2 (Debian):
status: Unknown → Fix Released
Michel Le Cocq (nomad-fr) wrote :

when you say next cycle it's version 19.04 or something else ? like 19.10 ?

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

Other bug subscribers

Remote bug watches

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