Bug 187273 - Crash: consecutive selection of encrypted messages without entering passphrase
Summary: Crash: consecutive selection of encrypted messages without entering passphrase
Status: RESOLVED DUPLICATE of bug 180741
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9.9
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-16 03:36 UTC by x3ri7yz02
Modified: 2009-09-30 22:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description x3ri7yz02 2009-03-16 03:36:25 UTC 
Version:           1.9.9 (using 3.5.10, Debian Package 4:3.5.10.dfsg.1-1+b1 (5.0))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.26-1-686

Kmail (via Kontact) crashes if user selects encrypted messages but does not enter a passphrase.

To reproduce:
From Kmail, select an encrypted message in the inbox.  Passphrase dialogue is presented, but instead select another encrypted message in the inbox.  Now hitting "Cancel" in the passphrase dialogue OR selecting another message in the inbox causes Kmail (Kontact) to crash.
Comment 1 Dario Andres 2009-09-28 02:52:44 UTC 
- Any chance to check this against KDE4 ? Thanks
Comment 2 x3ri7yz02 2009-09-28 03:53:23 UTC 
Sure thing.  There is still a problem. Tested with Kontact 1.4.4, Kmail 1.11.4 on KDE 4.2.4 (Debian packages) - still able to reproduce crash behaviour.  

Crash can be reproduced as original report or with the following steps:

1.  Select an encrypted message (Kontact prompts for passphrase)
2.  Select another (unencrypted) message. 
3.  Passphrase dialog box remains but is unnecessary, so click "cancel" - Kontact crashes

These steps also cause a crash:
1.  Select an encrypted message (Kontact prompts for passphrase)
2.  Select another encrypted message.  
3.  Enter passphrase - Kontact crashes.

Don't know how helpful this is, but backtrace shows:


Application: Kontact (kontact), signal SIGSEGV
[Current thread is 1 (Thread 0xb48d0920 (LWP 17087))]

Thread 2 (Thread 0xaf6eeb90 (LWP 17091)):
#0  0xb7fd0424 in __kernel_vsyscall ()
#1  0xb6b39fe1 in select () from /lib/i686/cmov/libc.so.6
#2  0xb7790c80 in QProcessManager::run (this=0x9f0ffa8) at io/qprocess_unix.cpp:296
#3  0xb76c1582 in QThreadPrivate::start (arg=0x9f0ffa8) at thread/qthread_unix.cpp:188
#4  0xb52334b5 in start_thread (arg=0xaf6eeb90) at pthread_create.c:300
#5  0xb6b41a5e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb48d0920 (LWP 17087)):
[KCrash Handler]
#6  0xb0ee336a in typeinfo for DwFieldBody () from /usr/lib/libmimelib.so.4
#7  0xb126a29e in KMReaderWin::parseMsg (this=0xc31e710, aMsg=0x50) at ../../kmail/kmreaderwin.cpp:1662
Backtrace stopped: frame did not save the PC
Comment 3 Dario Andres 2009-09-30 22:52:47 UTC 
The new backtrace is crash 180741. Thanks
Comment 4 Dario Andres 2009-09-30 22:54:38 UTC 

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