gnupg cannot decode an armored text with blank lines between text lines. I think it is related to the kgpg editor supplying some kind of "formatted copy" for firefox to paste to the gmail webmail. Reproducible: Always Steps to Reproduce: If I have an armored text in the editor (after encryption) and I want to copy it to a webmail like gmail (in firefox), I select the text and click Copy. Then I go to the gmail web form for new letter and paste the text. Actual Results: The text looks good in the gmail web form, but it is sent with a blank line after every text line. gnupg cannot decode an armored text with blank lines between text lines, and this is how recipients receive the letter. If the user sets the gmail web form to "Plain text only", then the blank lines are even visible in the web form. Then the user can remove there the blank lines manually, to get back the normal armored text. Expected Results: The armored text should be pasted in a way that it's send without extra blank lines, so recipients can decode it with gnupg or alike. I think it is related to the kgpg editor supplying some kind of "formatted copy" for firefox to paste to the gmail webmail. The only way I can get proper armored text into the gmail form is to select the text in the kgpg editor in clear, and in the traybar kgpg click "encrypt clipboard". The result encrypted text of that operation in the clipboard can be properly pasted into the gmail form and it's sent fine. That's why I conclude that the problem is only in the "Copy" operation of selected text from inside the kgpg editor. I consider it a major issue, because the very common path of encrypting text and pasting to a mailer, so popular as gmail in web, is broken.
I have the same problem... copy/past from kgpg to the webbrowser (Chrome in my case) is always broken with additional empty lines. I am using KDE 4.14.6 (Kubuntu 14.10). Another way to get a clear text is to copy the content of kgpg into kate and then into the Webbrowser.
Can you please try if the patch from bug 346983 also fixes this issue?
Bug is still present in KDE 4.14.9 (Fedora 22 KDE Spin).
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.