Bug 84028

Summary:	Crash when composing mail when sender has expired PGP key (even if not encrypting or signing)
Product:	[Unmaintained] kmail	Reporter:	Christian Esken <esken>
Component:	encryption	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version:	1.6.82
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	The Public Key ring needed for reproducing the problem

Description Christian Esken 2004-06-26 12:05:58 UTC

Version:           1.6.82 (using KDE 3.2.90 (3.3 alpha1, CVS >= 20040522), compiled sources)
Compiler:          gcc version 3.3.1 (SuSE Linux)
OS:                Linux (i686) release 2.4.21-99-athlon

I compose a message which works. I do not use encryption or signing for that message.
But as soon as I am finished composing and click "send" a message box appears:

"One or more of your configured OpenPGP encryption keys or S/MIME certificates is not usable for encryption. Please reconfigure your encryption keys and certificates for this identity in the identity configuration dialog.
If you choose to continue, and the keys are needed later on, you will be prompted to specify the keys to use."

I can either continue or cancel that dialog box - the result is the same: KMail crashes.

How to reproduce: Create a fresh ~/.gnupg directory and stick the attached pubring.gpg in it. Run KMail, compose a message and try to send it. The dialog box should appear, then click any of the 2 buttons => crash.


Chris

----------------------------------------------
Some extra information (probably not relevant):

Unfortunately I cannot supply a backtrace, as the "KDE Crash handler" does not show up. Also from gdb, I do not get a backtrace, because I get stuck in a "signal SIG43" loop as soon as I enter the composer. :-(

(gdb) run --nofork --nocrashhandler
[...]
kio (KDirWatch): Added Dir /home/chris/.kde/share/config for /home/chris/.kde/share/config/kabldaprc
kio (KDirWatch):  Setup DNotify (fd 128) for /home/chris/.kde/share/config

Program received signal SIG43, Real-time event 43.
[Switching to Thread 16384 (LWP 3388)]
0x422ba348 in open () from /lib/i686/libpthread.so.0
(gdb) c
Continuing.

Program received signal SIG43, Real-time event 43.
0x422ba348 in open () from /lib/i686/libpthread.so.0

Comment 1 Christian Esken 2004-06-26 12:08:48 UTC

Created attachment 6480 [details]
The Public Key ring needed for reproducing the problem

Comment 2 David Faure 2004-07-15 13:58:36 UTC

On Saturday 26 June 2004 12:06, Christian Esken wrote:
> How to reproduce: Create a fresh ~/.gnupg directory and stick the attached pubring.gpg in it. Run KMail, compose a message and try to send it. The dialog box should appear

This isn't enough to get the dialog to appear.
pubring.gpg is unrelated to the dialog, which says "One or more of *your* configured OpenPGP encryption keys".
So it's related to which key you selected in the KMail configuration dialog, for your email identity,
(is there a key selected there?) and it's related to which crypto backend you are using 
(see the last tab of the Security page). Which backend is selected there?

Comment 3 Christian Esken 2004-07-16 22:43:43 UTC

Well, that is confusing - I am wondering why *my* key is needed for encryption.  Well, I bet it is actually not needed. OK, enough of the theory and back to your questions.
1) Yes, I have selected a key. It is an OpenPGP key.
2) Hmm, currently there is NO backend selected. But I can actually still select an OpenPGP key. I think that is VERY strange: No backend selected, but I have a key.

I have just tested what heappens, if I enable and then disable the OpenPGP backend. Now the key has vanished and I cannot select a new key.

I would guess that it is a configuration file migration problem. Is there a migration script that would normally run for "normal" users (those who run releases instead of CVS versions)?

Comment 4 Till Adam 2004-07-18 17:00:03 UTC


*** This bug has been marked as a duplicate of 83093 ***

Comment 5 David Faure 2004-08-12 19:44:08 UTC

On Saturday 26 June 2004 12:06, Christian Esken wrote:
> Program received signal SIG43, Real-time event 43.

BTW, "handle SIG43 nostop" should help.

(not that I know what real-time event 43 is...)