Send an unencrypted reply to an encrypted message infinite loop
If I want to send an unencrypted reply to an encrypted message with spell check upon sending enabled, I'm stuck in an infinite loop and unable to send the message. I get the warning sheet titled "Attention: You're about to send an unencrypted reply to an encrypted message" as expected. When I click send anyway, I go through the spell check process, and when I try to send the message, the sheet pops up again. This loop continues indefinitely until I hit cancel, which results in being unable to send the message.
Comments are currently closed for this discussion. You can start a new one.
|?||Show this help|
|ESC||Blurs the current field|
|r||Focus the comment reply box|
|^ + ↩||Submit the comment|
You can use
Command ⌘ instead of
Control ^ on Mac
Support Staff 1 Posted by Steve on 27 Mar, 2015 11:26 PM
thanks a lot for this report.
We have a ticket for this problem. I connected this discussion with the existing ticket. That means, should this discussion get closed, it will be re-opened as soon as the ticket is closed. That way you'll receive a notification. Feel free to open a new discussions should you run into further problems or need assistance.
All the best,
2 Posted by Martin on 28 Mar, 2015 02:29 PM
Excellent, thanks Steve.
Support Staff 3 Posted by Steve on 28 Mar, 2015 04:46 PM
You're probably already aware, but as a workaround for the time being, you'd have to switch the Spellcheck setting away from "check on send" to something else.
We'll keep you posted as soon as we have news about this bug.
Steve closed this discussion on 28 Mar, 2015 04:46 PM.
Support Staff 4 Posted by Steve on 07 Apr, 2015 11:42 AM
this issue has been fixed. If you want to test the fix, please download our latest nightly GPG Suite. That page also has sig and SHA1 to verify the download.
Should the problem persist, please re-open this discussion. If you have other questions you can open a new one any time.
Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected. Thanks for helping us test this fix.
Steve closed this discussion on 07 Apr, 2015 11:42 AM.