Bug 361109 - kmail freezes with high cpu usage when sending signed messages with attachments
Summary: kmail freezes with high cpu usage when sending signed messages with attachments
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: crypto (show other bugs)
Version: 5.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-28 17:46 UTC by Christopher Suttles
Modified: 2022-11-26 05:15 UTC (History)
1 user (show)

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 Christopher Suttles 2016-03-28 17:46:06 UTC
When attempting to send an signed pgp message with attachment (8MB PDF), kmail prompts with a message box that asks "Some parts of this message will not be signed. Sending only partially signed messages might violate site policy. Sign all parts instead?" At this point, CPU usage hits 100%. System becomes frozen, however mouse is still useable. Clicking "Sign All Parts" does nothing, however clicking "Send As Is" sends the message in unencrypted form after nearly 1-2 minutes.

This seems to only happen with large attachments (greater than 5MB or so).

Reproducible: Sometimes

Steps to Reproduce:
1. Attempt to send signed pgp message with attachment 
2. At "Unsigned-Message Warning" dialog box, cpu hits 100% and system partially freezes
3. Can only send the email successfully if "Send As Is" is clicked.

Actual Results:  
Can't send emails fully signed. Getting high cpu usage and kmail become unresponsive for some time.

Expected Results:  
Email should be able to be sent as normal, with minimal cpu usage (or none).
Comment 1 DecentM 2016-11-08 03:41:30 UTC
This is also hanneing to me, also when sending a signed or encrypted and signed message.
Comment 2 Justin Zobel 2022-10-27 02:48:36 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-11-11 05:18:14 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-11-26 05:15:54 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!