Bug 326672

Summary:	selecting encrypt all in the unencrypted warning does not work and causes a crash
Product:	[Applications] kmail2	Reporter:	Arne Babenhauserheide <arne_bab>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	crash	CC:	montel, sknauss
Priority:	NOR	Keywords:	triaged
Version:	4.11.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	kmail-encrypt-all-crash-backtrace.txt

Description Arne Babenhauserheide 2013-10-26 10:55:19 UTC

see the steps to reproduce and the result:

Reproducible: Didn't try

Steps to Reproduce:
1. Set KMail to warn on sending unencrypted mail (maybe also to always sign - that’s my setting)
2. Write a mail, try to send it unencrypted (in my case signed)
3. In the unencrypted-warning click “encrypt all”
Actual Results:  
The key selection dialog shows the receiver keys (mine and the recipients) but not *my key* at the top (as it does in the regular encryption key selection).

Then a message pops up, telling me that I do not encrypt to myself, so I won’t be able to read the message (that’s wrong: my key is in the list of encryption keys - I *guess* that the message box does not get told what is my key).

When I tell it to encrypt anyway, KMail dies.

Expected Results:  
After clicking “encrypt all”, it should encrypt as usual.

Comment 1 Laurent Montel 2013-10-26 13:30:59 UTC

backtrace ?

Comment 2 Arne Babenhauserheide 2013-10-26 15:25:20 UTC

Dr. Konqui did not appear (I just reproduced it).

On the shell it prints this: 

*** KMail got signal 11 (Exiting)
kmail2(7351) KMKernel::dumpDeadLetters: Danger, using an event loop, this should no longer be happening! 

`gdb kmail` does not give me a backtrace, either.

Comment 3 Jekyll Wu 2013-10-27 05:48:28 UTC

Try this :

$ gdb kmail
gdb > set args --nofork
gdb > run 
gdb > ....

For more inforamtion,  see  http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Comment 4 Arne Babenhauserheide 2013-10-27 07:14:12 UTC

Created attachment 83145 [details]
kmail-encrypt-all-crash-backtrace.txt

Backtrace from the KMail Crash (thank you for the info how to create it!)

Comment 5 Sandro Knauß 2013-11-20 12:03:29 UTC

Please give 4.11.4 a try. This bug sounds like it can solved together with #314930.

Comment 6 Arne Babenhauserheide 2013-11-20 15:51:39 UTC

Thank you!

I can test the fix once 4.11.4 made its way into Gentoo testing.

Comment 7 Andrew Crouthamel 2018-09-25 03:48:53 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 set the bug status 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 8 Arne Babenhauserheide 2018-09-25 19:10:56 UTC

I no longer see this. Thank you for curating the bugs!