Summary: | Crash: consecutive selection of encrypted messages without entering passphrase | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | x3ri7yz02 |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra |
Priority: | NOR | ||
Version: | 1.9.9 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
x3ri7yz02
2009-03-16 03:36:25 UTC
- Any chance to check this against KDE4 ? Thanks 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 The new backtrace is crash 180741. Thanks *** This bug has been marked as a duplicate of bug 180741 *** |