Encryption: failed to generate keys

[realchrisolin]

Microsoft Windows [Version 10.0.26100.7171]
CopyQ v13.0.0

In Windows environments, after clicking the button to generate a new key, an error message is displayed:

failed to generate keys

This error is misleading as a new and valid encryption key can be located at
C:\Users\%USERNAME%\AppData\Roaming\copyq\copyq.pub. To resolve this issue, the key needs to be imported into Kleopatra:

After importing the key, a window will pop up prompting you to trust the key. You must trust it for encryption in CopyQ to work. Kleopatra should show the key in a certified status now:

At this point, close and reopen CopyQ. Encryption should work without any problem now.

(I opened this issue so anyone googling the error message will likely find this issue along with steps to fix as I don't expect there's anything that can be done upstream to automatically import the key in Kleopatra -- it may be better to flesh out these instructions to resolve this issue in the official docs.)

[hluk]

Using gpg in CopyQ is too complex, and the code is very difficult to maintain. I'm working on getting the encryption to work natively in CopyQ. It will be available in the next release. See: #3345

In the meantime, you can try the latest development build: https://ci.appveyor.com/project/hluk/copyq/builds/53312317/artifacts