[kmail2] [Bug 345396] New: Replying to or forwarding a signed/encrypted message can block the whole application
RJVB
rjvbertin at gmail.com
Sat Mar 21 17:46:35 GMT 2015
https://bugs.kde.org/show_bug.cgi?id=345396
Bug ID: 345396
Summary: Replying to or forwarding a signed/encrypted message
can block the whole application
Product: kmail2
Version: 4.13.3
Platform: MacPorts Packages
OS: OS X
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: composer
Assignee: kdepim-bugs at kde.org
Reporter: rjvbertin at gmail.com
Replying to or forwarding a message that was signed (or encrypted) with an
unknown key can block the whole application for minutes, as if it's "hung",
while the keyserver is queried.
Reproducible: Always
Steps to Reproduce:
1. Receive a message signed or encrypted with a key that is not known locally
2. Select the message in the message list
3. Hit 'f' (F) or r to forward the message or reply to it
Actual Results:
On OS X, the "beachball of death" appears quickly without any other sign of
progress, indicating that the application is no longer handling events. If the
configured keyserver is slow to respond for whatever reason, this situation
persists until the lookup succeeds, fails on the server, or times out. It is
only at that time that the composer window opens.
Expected Results:
When selecting the message in step 2), its contents are shown in the viewer
pane (if it's just signed, of course). The key lookup and ensuing validation
take place in the background.
The same thing should happen when replying or forwarding; I see no need to wait
for validation. In any case the application shouldn't hang, and provide a way
to interrupt the ongoing lookup (probably just by closing the composer window).
I'm marking this as "software hangs" because I have no way to be sure that the
software will NOT hang if the keyserver never replies.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Kdepim-bugs
mailing list