Version: 1.8.3 (using KDE 3.4.3, Kubuntu Package 4:3.4.3-0ubuntu2 ) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.12-10-386 If KMail is asking you for the passphrase to decrypt a mail with GnuPG and you choose another mail (possible in another folder, check) and then close the dialog, KMail crashes.
Can you paste the backtrace here, please?
I cannot reproduce this problem: it's impossible to select another email while the pinentry program is on the foreground (KMail 1.9.2 r522440).
This was with an inline (obsolete) encryption, so, it wasn't pineentry asking for the passphrase, it was kmail itself (I didn't even have pineentry installed at that time). I can provide a usefull backtrace because I am used pre-compiled packages.
Please do. It must be the same as the bug that makes KMail crash if you change messages while the read notification confirmation is showing.
Sorry, misspelled, I mean I can't provide a useful backtrace. Sorry :(
Does this problem still occur with KMail from KDE 3.5?
This problem is still current with all versions up to 3.5.5. Reproduction is very easy, although you have to be fast: 1. slow your computer down so that the crypto operation takes some time (e.g. compiling the kernel or KDE :-) or use a slower machine) 2. have kmail open and point to one email; pinentry should not have your password cached 3. select an email that is encrypted 4. now immediately select another email (e.g. click into another folder or so) *before* the pinentry prompt is shown 5. cancel pinentry's operation by hitting the cancel button -> kmail's popup is shown that a message cannot be decrypted -> now hit, say, cancel because you want to get rid of the message -> Segfault when the popup goes away It goes even funnier when the new email you selected is also encrypted and you cancel the new pinentry prompt -> two questions from kmail as described in step 5 are shown and after you clicked the last away, kmail dies.
I have the very same problem with KMail 1.9.7 on KDE 3.5.7. I basically just have to open a folder that contains at least one message that is encrypted. If I click on the encrypted message I get a dialog box asking me to enter the password for the key. With a OK and cancel button. If I now click on another mail without cancelling the dialog box first, kmail crashes. The second e-mail does not have to be in a different folder or be encrypted.
To clarify: Clicking on the second e-mail does not crash Kmail, however, closing the already open password prompt at this point does. A backtrace: #5 0x00000000 in ?? () #6 0xb4ec488f in KMReaderWin::parseMsg () from /usr/lib/libkmailprivate.so #7 0xb4ebfbd3 in KMReaderWin::displayMessage () from /usr/lib/libkmailprivate.so #8 0xb4ebfdce in KMReaderWin::updateReaderWin () from /usr/lib/libkmailprivate.so #9 0xb4ec2b4c in KMReaderWin::qt_invoke () from /usr/lib/libkmailprivate.so #10 0xb6f3cb10 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #11 0xb6f3d5f5 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #12 0xb72ceb94 in QTimer::timeout () from /usr/lib/libqt-mt.so.3 #13 0xb6f64282 in QTimer::event () from /usr/lib/libqt-mt.so.3 #14 0xb6ed136a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #15 0xb6ed3193 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #16 0xb7612ff2 in KApplication::notify () from /usr/lib/libkdecore.so.4 #17 0xb6e626c9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #18 0xb6ec41b1 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #19 0xb6e7719a in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #20 0xb6eec6e4 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #21 0xb6eec3e2 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #22 0xb6ed2f13 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #23 0x08059989 in ?? () #24 0xbfe52ac8 in ?? () #25 0x00000001 in ?? () #26 0x00000001 in ?? () #27 0x00000000 in ?? ()
This bug occurs as well for me, on ubuntu 8.04 amd64: on kmail 4:3.5.10-0ubuntu1~hardy2 It happens each time. 1. Select an OpenPGP encrypted email -> you are asked for passphrase 2. Select other email in the main window 3. go back to still open passphrase input window and click Close then crash. The crash seems to occur in different places. For example one back trace: [Thread debugging using libthread_db enabled] [New Thread 0x7f7e249e36f0 (LWP 16874)] [New Thread 0x4360e950 (LWP 16878)] [New Thread 0x42e0d950 (LWP 16877)] [New Thread 0x4260c950 (LWP 16876)] [New Thread 0x41e0b950 (LWP 16875)] [KCrash handler] #5 0x0000000000000020 in ?? () #6 0x00007f7e1d4fdf02 in QListViewItem (this=0x11db7c0, parent=0xf57ed0, label1=@0x7fff2ca34900, label2=@0x7fff2ca34910, label3=@0x7fff2ca34920, label4=@0x7fff2ca34930, label5=@0x7fff2ca34940, label6=@0x7fff2ca34950, label7=@0x7fff2ca34960, label8=@0x7fff2ca34970) at widgets/qlistview.cpp:599 #7 0x00007f7e24365121 in KMMimePartTreeItem (this=0x11db7c0, parent=0xf57ed0, node=0x11d7290, description=@0x7fff2ca34b30, mimetype=@0x7fff2ca34b20, encoding=<value optimized out>, size=0, revertOrder=false) at /build/buildd/kdepim-3.5.10/./kmail/kmmimeparttree.cpp:348 #8 0x00007f7e2438e842 in partNode::fillMimePartTree (this=0x11d7290, parentItem=0xf57ed0, mimePartTree=0x0, labelDescr=<value optimized out>, labelCntType=@0x7fff2ca34cc0, labelEncoding=@0x7fff2ca34cb0, size=0, revertOrder=32) at /build/buildd/kdepim-3.5.10/./kmail/partNode.cpp:506 #9 0x00007f7e2438200b in KMail::ObjectTreeParser::insertAndParseNewChildNode (this=0x7fff2ca35240, startNode=@0xe64a30, content=<value optimized out>, cntDesc=<value optimized out>, append=32) at /build/buildd/kdepim-3.5.10/./kmail/objecttreeparser.cpp:218 #10 0x00007f7e24386572 in KMail::ObjectTreeParser::processMultiPartEncryptedSubtype (this=0x7fff2ca35240, node=0xe64a30, result=@0x7f7e24374ed0) at /build/buildd/kdepim-3.5.10/./kmail/objecttreeparser.cpp:1265 #11 0x00007f7e2438a232 in process (this=<value optimized out>, otp=0xf57ed0, node=0x11db7c0, result=@0x7fff2ca34910) at /build/buildd/kdepim-3.5.10/./kmail/bodypartformatter.cpp:124 #12 0x00007f7e24381924 in KMail::ObjectTreeParser::parseObjectTree ( this=0x7fff2ca35240, node=0xe64a30) at /build/buildd/kdepim-3.5.10/./kmail/objecttreeparser.cpp:294 #13 0x00007f7e24274068 in KMReaderWin::parseMsg (this=0xa1f030, aMsg=0xf4ddb0) at /build/buildd/kdepim-3.5.10/./kmail/kmreaderwin.cpp:1588 #14 0x00007f7e2427474b in KMReaderWin::displayMessage (this=0xa1f030) at /build/buildd/kdepim-3.5.10/./kmail/kmreaderwin.cpp:1514 #15 0x00007f7e2427493f in KMReaderWin::updateReaderWin (this=0xa1f030) at /build/buildd/kdepim-3.5.10/./kmail/kmreaderwin.cpp:1449 #16 0x00007f7e24277432 in KMReaderWin::qt_invoke (this=0xa1f030, _id=48, _o=0x7fff2ca356e0) at ./kmreaderwin.moc:301 #17 0x00007f7e1d3fdfd0 in QObject::activate_signal (this=0xa1f168, clist=0xa8b8c0, o=0x7fff2ca356e0) at kernel/qobject.cpp:2359 #18 0x00007f7e1d3feb4e in QObject::activate_signal (this=0xa1f168, signal=2) at kernel/qobject.cpp:2328 #19 0x00007f7e1d778496 in QTimer::timeout (this=0xa1f168) at .moc/debug-shared-mt/moc_qtimer.cpp:82 #20 0x00007f7e1d423d83 in QTimer::event (this=0xa1f168, e=0x7fff2ca35b80) at kernel/qtimer.cpp:222 #21 0x00007f7e1d39633a in QApplication::internalNotify (this=0x7fff2ca36110, receiver=0xa1f168, e=0x7fff2ca35b80) at kernel/qapplication.cpp:2638 #22 0x00007f7e1d398093 in QApplication::notify (this=0x7fff2ca36110, receiver=0xa1f168, e=0x7fff2ca35b80) at kernel/qapplication.cpp:2361 #23 0x00007f7e1eacc6bd in KApplication::notify (this=0x7fff2ca36110, receiver=0xa1f168, event=0x7fff2ca35b80) at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550 #24 0x00007f7e1d32720e in QApplication::sendEvent (receiver=0xa1f168, event=0x7fff2ca35b80) at ../include/qapplication.h:523 #25 0x00007f7e1d389abc in QEventLoop::activateTimers (this=0x66c4a0) at kernel/qeventloop_unix.cpp:559 #26 0x00007f7e1d33c107 in QEventLoop::processEvents (this=0x66c4a0, flags=4) at kernel/qeventloop_x11.cpp:392 #27 0x00007f7e1d3b05bf in QEventLoop::enterLoop (this=0x66c4a0) at kernel/qeventloop.cpp:201 #28 0x00007f7e1d3b02ab in QEventLoop::exec (this=0x66c4a0) at kernel/qeventloop.cpp:148 #29 0x00007f7e1d397e00 in QApplication::exec (this=0x7fff2ca36110) at kernel/qapplication.cpp:2761 #30 0x0000000000402eb4 in main (argc=7, argv=<value optimized out>) at /build/buildd/kdepim-3.5.10/./kmail/main.cpp:110 Other back trace: [Thread debugging using libthread_db enabled] [New Thread 0x7f2d193996f0 (LWP 15738)] [New Thread 0x4263a950 (LWP 15742)] [New Thread 0x41398950 (LWP 15741)] [New Thread 0x40b97950 (LWP 15740)] [New Thread 0x41e39950 (LWP 15739)] [KCrash handler] #5 0x00007f2d17c83d20 in typeinfo for DwString () from /usr/lib/libmimelib.so.1 #6 0x00007f2d18c2a09a in KMReaderWin::parseMsg (this=0xa1d570, aMsg=0x11747a0) at /build/buildd/kdepim-3.5.10/./kmail/kmreaderwin.cpp:1594 #7 0x00007f2d18c2a74b in KMReaderWin::displayMessage (this=0xa1d570) at /build/buildd/kdepim-3.5.10/./kmail/kmreaderwin.cpp:1514 #8 0x00007f2d18c2a93f in KMReaderWin::updateReaderWin (this=0xa1d570) at /build/buildd/kdepim-3.5.10/./kmail/kmreaderwin.cpp:1449 #9 0x00007f2d18c2d432 in KMReaderWin::qt_invoke (this=0xa1d570, _id=48, _o=0x7fff213ed0a0) at ./kmreaderwin.moc:301 #10 0x00007f2d11db3fd0 in QObject::activate_signal (this=0xa1d6a8, clist=0xa8af20, o=0x7fff213ed0a0) at kernel/qobject.cpp:2359 #11 0x00007f2d11db4b4e in QObject::activate_signal (this=0xa1d6a8, signal=2) at kernel/qobject.cpp:2328 #12 0x00007f2d1212e496 in QTimer::timeout (this=0xa1d6a8) at .moc/debug-shared-mt/moc_qtimer.cpp:82 #13 0x00007f2d11dd9d83 in QTimer::event (this=0xa1d6a8, e=0x7fff213ed540) at kernel/qtimer.cpp:222 #14 0x00007f2d11d4c33a in QApplication::internalNotify (this=0x7fff213edad0, receiver=0xa1d6a8, e=0x7fff213ed540) at kernel/qapplication.cpp:2638 #15 0x00007f2d11d4e093 in QApplication::notify (this=0x7fff213edad0, receiver=0xa1d6a8, e=0x7fff213ed540) at kernel/qapplication.cpp:2361 #16 0x00007f2d134826bd in KApplication::notify (this=0x7fff213edad0, receiver=0xa1d6a8, event=0x7fff213ed540) at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550 #17 0x00007f2d11cdd20e in QApplication::sendEvent (receiver=0xa1d6a8, event=0x7fff213ed540) at ../include/qapplication.h:523 #18 0x00007f2d11d3fabc in QEventLoop::activateTimers (this=0x66c540) at kernel/qeventloop_unix.cpp:559 #19 0x00007f2d11cf2107 in QEventLoop::processEvents (this=0x66c540, flags=4) at kernel/qeventloop_x11.cpp:392 #20 0x00007f2d11d665bf in QEventLoop::enterLoop (this=0x66c540) at kernel/qeventloop.cpp:201 #21 0x00007f2d11d662ab in QEventLoop::exec (this=0x66c540) at kernel/qeventloop.cpp:148 #22 0x00007f2d11d4de00 in QApplication::exec (this=0x7fff213edad0) at kernel/qapplication.cpp:2761 #23 0x0000000000402eb4 in main (argc=7, argv=<value optimized out>) at /build/buildd/kdepim-3.5.10/./kmail/main.cpp:110
Hi Can someone verify that we get the same with QT 4.5 and KDE 4.2.1? Kubuntu jaunty have this but it is still in alpha release but seems to work ok for me and fixes a somewhat similar bug 180741 for me. Be careful and check if it is ok for you to upgrade if you want to do this. They say there are issues with Xorg and fglrx driver and switch knetworkmanager to the applet if you use it. Just a suggestion, hope it helps, otherwise it will just provide a updated backtrace.
Seems fixed in KDE 4.3, as I cannot select another mail from the main window while the passkey entry is open.
Same bug still happens even now on ubuntu 9.10. This bug is known from 2006 and still not fixed in 2010.
*** This bug has been marked as a duplicate of bug 180741 ***