Hello Jamie,
I can't reproduce this issue.
Am 06.08.23 um 16:10 schrieb Jamie McClelland:
After upgrading to 115.1.0, when sending a message with "Digitally sign"
selected I consistently receive an error that "Sending of the message
failed." (When
just encrypting it works fine.)
The error console reports:
CryptoAPI.sync() failed result: Error: rnp_op_encrypt_add_signature failed
encryptAndOrSign chrome://openpgp/content/modules/RNP.jsm:3526
sync chrome://openpgp/content/modules/cryptoAPI/interface.js:56
encryptMessageStart chrome://openpgp/content/modules/encryption.jsm:446
finishCryptoEncapsulation
chrome://openpgp/content/modules/mimeEncrypt.jsm:516
createMessageFile resource:///modules/MimeMessage.jsm:90
interface.js:46:17
Error: failure in finishCryptoEncapsulation, exitCode: -1
finishCryptoEncapsulation
chrome://openpgp/content/modules/mimeEncrypt.jsm:537
createMessageFile resource:///modules/MimeMessage.jsm:90
mimeEncrypt.jsm:554:15
mimeEncrypt.js: caught exception: Error
Message: 'failure in finishCryptoEncapsulation, exitCode: -1'
File: chrome://openpgp/content/modules/mimeEncrypt.jsm
Line: 537
Stack:
finishCryptoEncapsulation@chrome://openpgp/content/modules/mimeEncrypt.jsm:537:15
createMessageFile@resource:///modules/MimeMessage.jsm:90:27
Error: failure in finishCryptoEncapsulation, exitCode: -1
mimeEncrypt.jsm:537:15
finishCryptoEncapsulation
chrome://openpgp/content/modules/mimeEncrypt.jsm:537
createMessageFile resource:///modules/MimeMessage.jsm:90
InterpretGeneratorResume self-hosted:1455
AsyncFunctionNext self-hosted:852
mailnews.send: NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS: [JavaScript Error: "failure in finishCryptoEncapsulation,
exitCode: -1" {file: "chrome://openpgp/content/modules/mimeEncrypt.jsm" line:> 537}]'[JavaScript Error:
"failure in finishCryptoEncapsulation, exitCode: -1" {file:
"chrome://openpgp/content/modules/mimeEncrypt.jsm" line: 537}]' when calling method:
[nsIMsgComposeSecure::finishCryptoEncapsulation]
createMessageFile resource:///modules/MimeMessage.jsm:90
MessageSend.jsm:137:32
createAndSendMessage resource:///modules/MessageSend.jsm:137
mailnews.send: Sending failed; , exitCode=2153185313, originalMsgURI=
MessageSend.jsm:362:32
fail resource:///modules/MessageSend.jsm:362
createAndSendMessage resource:///modules/MessageSend.jsm:145
Error: rnp_op_encrypt_add_signature failed RNP.jsm:3526:21
You don't give any further information so it's difficult to give some
good advice.
There are some general suggestions how to narrow down potential issues
while working with a somehow dysfunctional Thunderbird application in
the Debian Wiki.
https://wiki.debian.org/Thunderbird#Bug_Reporting_.2F_Issues
Taking parts of the log from your error messages let me think it's not a
issue within Thunderbird itself, it looks like you've configured
Thunderbird to use GPG and not the internal crypto handling.
So far I remember you need ensure you have commented out this line in
~/.gnupg/gpg-agent.conf
$ grep pinentry ~/.gnupg/gpg-agent.conf
#allow-loopback-pinentry
And also don't have set "pinentry-mode loopback" in ~/.gnupg/gpg.conf.
To see more information you will need to enable some debugging.
https://www.gnupg.org/documentation/manuals/gpgme/Debugging.html
e.g.
$ GPGME_DEBUG=9:~/gpgme.log thunderbird --jsconsole
--
Regards
Carsten
