[pkg-gnupg-maint] Bug#801247: Info received (pinentry-gnome3: No PIN dialog)

Wilmer van der Gaast wilmer at gaast.net
Sun Feb 21 20:02:28 UTC 2016


I just had the same problem. I've straced gpg-agent and its child 
processes which resulted in a 5.1MByte strace dump though I'd rather not 
share it blindly.

I do see the following things in it:

7105  connect(9, {sa_family=AF_LOCAL, sun_path=@"/tmp/dbus-xNLgc87fg9"}, 
23) = -1 ECONNREFUSED (Connection refused)
7103  write(2, "\n** (pinentry:7103): WARNING **: couldn't create prompt 
for gnupg passphrase: Could not connect: Connection refused\n", 116) = 116
7102  write(3, "2016-02-21 19:56:43 gpg-agent[4656] DBG: error calling 
pinentry: Operation cancelled <Pinentry", 94) = 94

Some of that is in logs as you can see, but the connection refused to 
being dbus may be helpful information. I have no file named /tmp/dbus-* 
though to me the @ looks like it's actually the anonymous Unix domain 
socket namespace?

Happy to look at other things if it helps. For now fortunately I've got 
my SSH auth working again with pinentry-gtk-2.


Wilmer v/d Gaast.



More information about the pkg-gnupg-maint mailing list