Bug 98762

Summary: crash on changing from pgp to other pgp in inbox without closing the 1st password prompt
Product: [Applications] kmail Reporter: mik <maiqui>
Component: encryptionAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash    
Priority: NOR    
Version: 1.7.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description mik 2005-02-07 12:58:38 UTC
Version:           1.7.2 (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-6)
OS:                Linux (i686) release 2.6.9-2-k7

Hi,

this bug seems to be caused beacude that the prompt of password for a pgp email doent close automaticaly when you change to another message in the inbox.

I find this big doing the following.

1) I have two pgp messagesin mi inbox.

2) I click on one of them and the password prompt apears.

3) I dont do anithing with that prompt.

4) I click to another pgp message.

5) a new propmt apears. But the old one reminds in the back.

6) I close the new prompt.

7) I type my pass in the old prompt, and kmail closes.

here is the trase

no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1244704640 (LWP 4846)]
(no debugging symbols found)
"kmail" 248L, 8463C 

Ok.

I think the prompt must be automaticaly closed when you stop watching the corresponding pgp email.

hope this help.

Kmail works verry good.
thanks

mike
Comment 1 Stefan Monov 2007-02-06 00:34:56 UTC
Please install debug symbols and post a new backtrace. This one is useless ;)
Thanks.
Comment 2 Rolf Eike Beer 2007-09-19 18:58:56 UTC
This is likely a duplicate of either bug:53185 or bug:92737. Since there is no more input from the reporter and the original backtrace is useless I'll close it.