On Thu, Jun 04, 2015 at 08:38:27PM -0400, Daniel Kahn Gillmor wrote: > What's particularly weird is that this file doesn't seem to have changed > since 0.9.2, and i can't seem to reproduce the problem with > pinentry-gtk-2. What was the last version of pinentry-gtk-2 that you > used that didn't have this problem?
I only saw this problem yesterday (local time), as it prevented me from running git commit -S, so according to dpkg.log that means it first appeared in 0.9.3-1 or 0.9.3-2 (time in UTC): 2015-06-03 01:16:34 upgrade pinentry-gtk2:amd64 0.9.2-1 0.9.3-1 2015-06-03 01:16:34 status half-configured pinentry-gtk2:amd64 0.9.2-1 2015-06-03 01:16:34 status unpacked pinentry-gtk2:amd64 0.9.2-1 2015-06-03 01:16:34 status half-installed pinentry-gtk2:amd64 0.9.2-1 2015-06-03 01:16:34 status half-installed pinentry-gtk2:amd64 0.9.2-1 2015-06-03 01:16:34 status unpacked pinentry-gtk2:amd64 0.9.3-1 2015-06-03 01:16:34 status unpacked pinentry-gtk2:amd64 0.9.3-1 2015-06-04 01:37:00 upgrade pinentry-gtk2:amd64 0.9.3-1 0.9.3-2 2015-06-04 01:37:00 status half-configured pinentry-gtk2:amd64 0.9.3-1 2015-06-04 01:37:00 status unpacked pinentry-gtk2:amd64 0.9.3-1 2015-06-04 01:37:00 status half-installed pinentry-gtk2:amd64 0.9.3-1 2015-06-04 01:37:00 status half-installed pinentry-gtk2:amd64 0.9.3-1 2015-06-04 01:37:00 status unpacked pinentry-gtk2:amd64 0.9.3-2 2015-06-04 01:37:00 status unpacked pinentry-gtk2:amd64 0.9.3-2 I suspect it's the former, since I probably upgraded on the 3rd, and due to gpg-agent's 86400-second passphrase caching, I wouldn't have been prompted again until probably around 23:00 on the 3rd or 00:00 on the 4th. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature