On 09.06.17 19:45, Christian Riechers wrote: > On 6/8/17 8:44 AM, Patrick Brunschwig wrote: >> On 07.06.17 23:30, Christian Riechers wrote: >>> On 6/6/17 8:55 PM, Christian Riechers wrote: >>>> On 6/6/17 12:40 PM, Patrick Brunschwig wrote: >>>>> On 06.06.17 10:34, Christian Riechers wrote: >>>>>> Win7, TB54.0b3, Enigmail nightly build 2017-06-06, gpg4win 3.0.0 >>>>>> beta232, gnupg 2.1.19 >>>>>> >>>>>> Starting Thunderbird - Menu button - Enigmail - Key Management >>>>>> The window opens, showing 'Loading keys, please wait ...' at the bottom, >>>>>> but no keys are shown. See screenshot. >>>>>> http://i.imgur.com/hd77j1L.jpg >>>>>> >>>>>> There is one hanging gpg.exe process in Windows Task Manager. >>>>>> Upon closing Thunderbird it crashes. >>>>>> https://crash-stats.mozilla.com/report/index/e7a46c58-14ed-4b89-8eac-920220170606 >>>>> >>>>> I'm sorry, but Mozilla crashes don't help me in any way. Enigmail is >>>>> written in JavaScript, but the crashes only report the status of native >>>>> libraries and threads. >>>>> >>>>> If this happens again, please create & save a debug log file before you >>>>> close Thunderbird. >>>> >>>> I regret to tell, but I cannot reproduce this at the moment. I'll >>>> capture the debug log if this happens again. >>> >>> Problem reproduced. >>> I sent a debug log via PM. >> >> Thanks. I check the log files you sent me. The log files clearly show >> that the gpg process to list the keys doesn't return. This may be >> because the other running gpg (or gpg-agent) process blocks something. >> >> I actually believe that this is an error in gpg4win (as you're using >> gpg4win 3.0 beta): there must not be two gpg-agent processes at the same >> time. Enigmail does not start gpg-agent (as you can see in the log files >> you sent me), and gpg should always connect to the same agent. A new >> agent would only be started if there is no running agent. >> >> I would report this to the gpg4win team. > > Good point. I removed gpg4win and installed the vanilla gnupg 2.1.19 > binary package for Windows. I think this is supposed to work. > > With that things look a whole lot better, Key Management opens with all > keys visible, and no more orphan gpg.exe or gpg-agent.exe processes in > task manager. > > However, there's still a problem with sending an encrypted message. It > fails with the following error: > > Send operation aborted. > Error - encryption command failed > > This looks like a déjà vu. But as per your previous advice, I already > re-selected my key IDs in the account manager such that they are are > shown as fingerprints. > I can open messages encrypted to my public key. > > I sent you another debug log. > Thanks again.
Gpg complains about not being able to find the secret key for 0x4B81B3234232DCD2EC32FD4FE045FE37AD62C09F. I'd assume that's because GnuPG 2.1 uses a different type of keyring format that GnuPG 2.0. You can't simply uninstall GnuPG 2.1, install GnuPG 2.0 and expect that keys will continue to work like before. You have to export your keys from GnuPG 2.1, and then re-import them into GnuPG 2.0 -Patrick
signature.asc
Description: OpenPGP digital signature
_______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
