On 15/10/16 01:45, Daniel Kahn Gillmor wrote:
> On Fri 2016-10-14 16:56:37 -0400, OmegaPhil wrote:
>> On 14/10/16 00:28, Daniel Kahn Gillmor wrote:
>>> On Thu 2016-10-13 14:09:16 -0400, OmegaPhil wrote:
>>>> As soon as I did a killall to have gpg-agent load the new
>>>> configuration and try again, it worked - I know that gpg2 stuff has
>>>> updated recently, and my uptime is ~11d, so perhaps the update scripts
>>>> don't kill off gpg-agent when theres some incompatible change?
>>> That's right, the package upgrade scripts make no attempt to restart
>>> long-running user processes, for reasons i suspect you can imagine :)
>>> Can you review /var/log/dpkg.log to see what versions of gpg-agent you
>>> might have been running initially?  I'm glad it's working for you now,
>>> anyway, though i'm still in the dark as to why it wasn't working for you
>>> before.
>> Latest mentions of gnupg-agent:
>> =================================================
>> /var/log/dpkg.log:2016-10-02 08:11:27 upgrade gnupg-agent:amd64 2.1.11-7 
>> 2.1.15-3
> You wrote ~11d on the 13th.  This upgrade is from the 2nd, ~11d before
> the report.  Can you tell me whether this upgrade happend before or
> after the boot that led you into the 11d uptime?  If it happened after
> then yes, you were most likely running the older gpg-agent without
> restarting it, which would explain the failures you saw.
> fwiw, gpg should provide warning messages to stderr if it discovers it's
> talking to an older agent, but if you only accessed it through enigmail
> maybe those warning messages weren't propagated through to where you
> could easily see them.
>            --dkg

No, 'old gpg-agent was running' doesn't seem to be the right explanation
for this. The upgrade happened at 2016-10-02 08:11:27, however October
the 2nd looks like monthly reboot day, since there was a reboot from a
v4.5 kernel into v4.6 at 19:35:49, and then v4.7 at 19:40:19 (I'm
running v4.7.5-1 atm).

I'd like to say that any complaints from gpg-agent would cause that
Enigmail dialog to pop up, e.g. the 4 repeats of the dialog originally
suggestively match the 4 lines reported to .xsession-errors.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to