Bug 347668 - Cannot send unencrypted mail, window hanging
Summary: Cannot send unencrypted mail, window hanging
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-13 13:34 UTC by Nolaan
Modified: 2018-01-31 16:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nolaan 2015-05-13 13:34:18 UTC
The compose window hangs.
First there's this long lasting bug when you have a pgp/gpg key for a contact where it keeps asking you which key you wanna use even though you keep pressing Cancel. Then it brings you to the next dialog where it ask if you want to use the previous that you didn't want but that it selected anyway. Now you have to delete the key and select none in order to send it unencrypted; other combination will fail. And the last dialog ask you if you really want to send an unencrypted email, click yes the window becomes grey.

Reproducible: Always

Steps to Reproduce:
1.Write an email to a contact you posess a gpg key
2. Send the email


Actual Results:  
Grey window, no mail sent

Expected Results:  
Send the email
Comment 1 Denis Kurz 2017-06-23 20:01:52 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:51:55 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.