crash when selecting email when input-passphrase/pin (OpenPGP) window is open and then canceled

Bug #300127 reported by LimCore on 2008-11-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE PIM
Unknown
High
kdepim (Ubuntu)
Undecided
Unassigned

Bug Description

https://bugs.kde.org/show_bug.cgi?id=125512

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.

ubuntu 8.04 amd64
kmail 4:3.5.10-0ubuntu1~hardy2

[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

LimCore (limcore) wrote :
description: updated
Changed in kdepim:
status: New → Confirmed
Changed in kdepim:
status: Unknown → Confirmed
Download full text (7.1 KiB)

Version: (using Devel)
Installed from: Compiled sources

kdepim-4.1.96-1.fc10.x86_64

Application: KMail (kmail), signal SIGILL
0x0000003840aa7f81 in nanosleep () from /lib64/libc.so.6
Current language: auto; currently c
[Current thread is 1 (Thread 0x7f4f87d99800 (LWP 4780))]

Thread 9 (Thread 0x7f4f7cf3b950 (LWP 11461)):
#0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:217
#1 0x00007f4f7be4aa91 in ?? () from /usr/lib64/libxine.so.1
#2 0x00000038416073da in start_thread (arg=<value optimized out>) at pthread_create.c:297
#3 0x0000003840ae62bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112

Thread 8 (Thread 0x7f4f7724a950 (LWP 11462)):
#0 0x0000003840adc886 in __poll (fds=0x20ae5c0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x000000384223ae08 in g_main_context_poll () at gmain.c:3091
#2 g_main_context_iterate (context=0x283dde0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2773
#3 0x000000384223b12b in IA__g_main_context_iteration (context=0x283dde0, may_block=1) at gmain.c:2841
#4 0x00000039e636a7be in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4
#5 0x00000039e6340cb2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4
#6 0x00000039e6340e3d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#7 0x00000039e62568e8 in QThread::exec () from /usr/lib64/libQtCore.so.4
#8 0x00007f4f7c0a4094 in Phonon::Xine::XineThread::run (this=0x25a7340) at /usr/src/debug/phonon-4.2.96/xine/xinethread.cpp:143
#9 0x00000039e6259852 in ?? () from /usr/lib64/libQtCore.so.4
#10 0x00000038416073da in start_thread (arg=<value optimized out>) at pthread_create.c:297
#11 0x0000003840ae62bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
Current language: auto; currently asm

Thread 7 (Thread 0x7f4f76849950 (LWP 11463)):
#0 0x0000003840adc886 in __poll (fds=0x28ca5f0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x00007f4f77cb6034 in ?? () from /usr/lib64/libpulse.so.0
#2 0x00007f4f77ca6c62 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0
#3 0x00007f4f77ca7015 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0
#4 0x00007f4f77ca708a in pa_mainloop_run () from /usr/lib64/libpulse.so.0
#5 0x00007f4f77cb60a2 in ?? () from /usr/lib64/libpulse.so.0
#6 0x00007f4f77ce7201 in ?? () from /usr/lib64/libpulse.so.0
#7 0x00000038416073da in start_thread (arg=<value optimized out>) at pthread_create.c:297
#8 0x0000003840ae62bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
Current language: auto; currently c

Thread 6 (Thread 0x7f4f71e47950 (LWP 11464)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1 0x00007f4f7be5bc43 in ?? () from /usr/lib64/libxine.so.1
#2 0x00000038416073da in start_thread (arg=<value optimized out>) at pthread_create.c:297
#3 0x0000003840ae62bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112

Thread 5 (Thread 0x7f4f70dbf950 (LWP 11465)):
#0 0x0000003840adeaa2 in select () from /lib64/libc.so.6
#1 0x00007f4f7be72b54 in xine_usec_sleep () from /usr/lib...

Read more...

Seems repeatable - crash when trying to delete a message

This sounds like a packaging or compiler bug. Maybe kmail was build against a newer version of Qt than the version that is installed in your computer?

*** Bug 182160 has been marked as a duplicate of this bug. ***

The reporter of bug 182160 says he can reproduce the bug

I haven't seen this in a while now. I believe it's fixed here.

kdepim-4.2.0-2.fc10.x86_64
qt-4.4.3-10.fc10.x86_64

Same with local recompile.
qt4 4.4.3-0ubuntu1.1
g++ 4.3.2 (Ubuntu 4.3.2-1ubuntu12)

Will try with g++ 4.2 and 4.1 if that will work.

(gdb) bt
#0 0x00007f4974ae7390 in typeinfo for DwFieldBody () from /usr/lib/libmimelib.so.4
#1 0x00007f497d2d67ed in KMReaderWin::parseMsg (this=0x25fddf0, aMsg=0x31665f0) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1628
#2 0x00007f497d2c4537 in KMReaderWin::displayMessage (this=0x25fddf0) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1555
#3 0x00007f497d2c4725 in KMReaderWin::updateReaderWin (this=0x25fddf0) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1495
#4 0x00007f497d2d1bf5 in KMReaderWin::qt_metacall (this=0x25fddf0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff8676ac20)
    at /home/johan/dev/kde/kdepim-4.2.0/obj-x86_64-linux-gnu/kmail/kmreaderwin.moc:164
#5 0x00007f4979de6134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#6 0x00007f4979de0a43 in QObject::event () from /usr/lib/libQtCore.so.4
#7 0x00007f497a4f5c3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#8 0x00007f497a4fd9ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#9 0x00007f497e1593eb in KApplication::notify (this=0x7fff8676b730, receiver=0x25fde88, event=0x7fff8676b2d0)
    at /build/buildd/kde4libs-4.2.0/kdeui/kernel/kapplication.cpp:307
#10 0x00007f4979dd1d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#11 0x00007f4979dfdab6 in ?? () from /usr/lib/libQtCore.so.4
#12 0x00007f4979dfa1fd in ?? () from /usr/lib/libQtCore.so.4
#13 0x00007f49714d0d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#14 0x00007f49714d450d in ?? () from /usr/lib/libglib-2.0.so.0
#15 0x00007f49714d46cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#16 0x00007f4979dfa15f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#17 0x00007f497a587a6f in ?? () from /usr/lib/libQtGui.so.4
#18 0x00007f4979dd0682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#19 0x00007f4979dd080d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#20 0x00007f4979dd2cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#21 0x000000000040309b in main (argc=<value optimized out>, argv=<value optimized out>) at /home/johan/dev/kde/kdepim-4.2.0/kmail/main.cpp:146

Get the same with 4.2 and 4.1
gcc version 4.2.4 (Ubuntu 4.2.4-3ubuntu4)
gcc version 4.1.3 20080623 (prerelease) (Ubuntu 4.1.2-23ubuntu3)

Any more ideas? Recompile Qt?
Is it handling signals correctly when another signal arrive to open next message when it is currently working on opening the first message at the same time. Using any non reentrant code?

Created attachment 30741
4.1 and 4.2 dbg

By waiting for the current message to fully display before selecting the next message will avoid the crash. No problem deleting mails for me. I will try to create a testcase-mail later and see if I can reproduce it in a clean account and computer.

Download full text (4.7 KiB)

Pasting the backtraces (it is a lot easier to find duplicates if they are as comments).

gcc version 4.2.4 (Ubuntu 4.2.4-3ubuntu4)
(gdb) bt
#0 0x00007f066d9ad420 in typeinfo for DwTokenString () from /usr/lib/libmimelib.so.4
#1 0x00007f06761af83c in KMReaderWin::parseMsg (this=0x2902a50, aMsg=0x33565d0) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1628
#2 0x00007f06761aaca5 in KMReaderWin::displayMessage (this=0x2902a50) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1555
#3 0x00007f06761aaf24 in KMReaderWin::updateReaderWin (this=0x2902a50) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1495
#4 0x00007f06761b433a in KMReaderWin::qt_metacall (this=0x2902a50, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7f62baf0)
    at /home/johan/dev/kde/kdepim-4.2.0/obj-x86_64-linux-gnu/kmail/kmreaderwin.moc:164
#5 0x00007f0672cb2134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#6 0x00007f0672caca43 in QObject::event () from /usr/lib/libQtCore.so.4
#7 0x00007f06733c1c3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#8 0x00007f06733c99ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#9 0x00007f06770183eb in KApplication::notify (this=0x7fff7f62c5f0, receiver=0x2902ae8, event=0x7fff7f62c1a0)
    at /build/buildd/kde4libs-4.2.0/kdeui/kernel/kapplication.cpp:307
#10 0x00007f0672c9dd61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#11 0x00007f0672cc9ab6 in ?? () from /usr/lib/libQtCore.so.4
#12 0x00007f0672cc61fd in ?? () from /usr/lib/libQtCore.so.4
#13 0x00007f066a390d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#14 0x00007f066a39450d in ?? () from /usr/lib/libglib-2.0.so.0
#15 0x00007f066a3946cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#16 0x00007f0672cc615f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#17 0x00007f0673453a6f in ?? () from /usr/lib/libQtGui.so.4
#18 0x00007f0672c9c682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#19 0x00007f0672c9c80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#20 0x00007f0672c9ecbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#21 0x000000000040300a in main (argc=<value optimized out>, argv=<value optimized out>) at /home/johan/dev/kde/kdepim-4.2.0/kmail/main.cpp:146

/usr/lib/libmimelib.so.4.2.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped
250752 2009-01-30 08:51 /usr/lib/libmimelib.so.4.2.0

gcc version 4.1.3 20080623 (prerelease) (Ubuntu 4.1.2-23ubuntu3)
(gdb) bt
#0 0x00007f14da23d0a0 in typeinfo for DwTokenString () from /usr/lib/libmimelib.so.4
#1 0x00007f14e2a40444 in KMReaderWin::parseMsg (this=0x1a77990, aMsg=0x24c4480) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1628
#2 0x00007f14e2a3b92f in KMReaderWin::displayMessage (this=0x1a77990) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1555
#3 0x00007f14e2a3bba4 in KMReaderWin::updateReaderWin (this=0x1a77990) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1495
#4 0x00007f14e2a4474d in KMReaderWin::qt_metacall (this=0x1a77990, _c=QMetaObject::InvokeMetaM...

Read more...

*** Bug 182853 has been marked as a duplicate of this bug. ***

Download full text (5.3 KiB)

< Pasting the backtraces (it is a lot easier to find duplicates if they are as comments).

They showed the same thing as the first I already posted so I think they are not of much use then for reference.

Tried the same messages with a new user. Messages show up much faster when changing between them and I'm not able reproduce it then. So there must be some combination of things that slows it down to create the problem.

Tried to comment out the lines at kmail/kmreaderwin.cpp:1628
Where we get the crash I think.

  // store encrypted/signed status information in the KMMessage
  // - this can only be done *after* calling parseObjectTree()
  KMMsgEncryptionState encryptionState = mRootNode->overallEncryptionState();
  KMMsgSignatureState signatureState = mRootNode->overallSignatureState();
//#! HERE 1628 !## aMsg->setEncryptionState( encryptionState );
  // Don't reset the signature state to "not signed" (e.g. if one canceled the
  // decryption of a signed messages which has already been decrypted before).
// if ( signatureState != KMMsgNotSigned ||
// aMsg->signatureState() == KMMsgSignatureStateUnknown ) {
// aMsg->setSignatureState( signatureState );
// }

But instead I now get a crash at another place. But it might help to explain the first one.

#0 DwHeaders::FindField (this=0x646f42646c656946, aFieldName=0x3573138 "Message-Id") at /home/johan/dev/kde/kdepim-4.2.0/mimelib/headers.cpp:287
#1 0x00007fd6a12f2770 in KMMessage::headerField (this=0x2255830, aName=@0x7fffaa8684c0) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmmessage.cpp:2231
#2 0x00007fd6a12f61d0 in KMMessage::msgId (this=0x2255830) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmmessage.cpp:2121
#3 0x00007fd6a13f78e0 in KMReaderWin::parseMsg (this=0x18e8f10, aMsg=0x2255830) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1708
#4 0x00007fd6a13e5537 in KMReaderWin::displayMessage (this=0x18e8f10) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1555
#5 0x00007fd6a13e5725 in KMReaderWin::updateReaderWin (this=0x18e8f10) at /home/johan/dev/kde/kdepim-4.2.0/kmail/kmreaderwin.cpp:1495
#6 0x00007fd6a13f2bf5 in KMReaderWin::qt_metacall (this=0x18e8f10, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffaa868d10)
    at /home/johan/dev/kde/kdepim-4.2.0/obj-x86_64-linux-gnu/kmail/kmreaderwin.moc:164
#7 0x00007fd69df17134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#8 0x00007fd69df11a43 in QObject::event () from /usr/lib/libQtCore.so.4
#9 0x00007fd69e626c3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#10 0x00007fd69e62e9ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#11 0x00007fd6a22605db in KApplication::notify () from /usr/lib/libkdeui.so.5 ...

Read more...

Download full text (30.9 KiB)

kmail(4027) KMail::lockOrDie: oldPid= 3862
kmail(4027) KMKernel::KMKernel:
kmail(4027) KWallet::Wallet::openWallet: Pass a valid window to KWallet::Wallet::openWallet().
kmail(4027) KMailApplication::newInstance:
kmail(4027) KMailApplication::newInstance: Delaying instance creation.
kmail(4027) KMKernel::init: foldersPath (from config): "/home/johan/.kde/share/apps/kmail/mail"
kmail(4027) KMKernel::identityManager:
kmail(4027) Sonnet::Loader::loadPlugin: Successfully loaded plugin: "kspell_hspell.desktop"
kmail(4027) Sonnet::Loader::loadPlugin: Successfully loaded plugin: "kspell_enchant.desktop"
kmail(4027) KMFilterMgr::KMFilterMgr: pPopFilter set
kmail(4027) KWallet::Wallet::openWallet: Pass a valid window to KWallet::Wallet::openWallet().
kmail(4027) KMFolderMaildir::createIndexFromContents: Creating index for "/home/johan/.kde/share/apps/kmail/autosave"
kmail(4027) KMFolderMaildir::createIndexFromContents: Creating index for "/home/johan/.kde/share/apps/kmail/autosave"
kmail(4027) KMailApplication::newInstance:
kmail(4027) KMKernel::openReader:
kmail(4027) KMReaderWin::KMReaderWin: Entering function
kmail(4027) KMReaderWin::createWidgets: Entering function
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x164f9f0)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QWidget(0x164f980)
kmail(4027) KMReaderWin::setStyleDependantFrameWidth: Entering function
kmail(4027) KMReaderWin::createActions: Entering function
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x195efb0)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x19a9390)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x19ad7e0)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x1987890)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x1980b30)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x1972b70)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x195e070)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x193ff60)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x1980d70)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x19b0f00)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x19ab660)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x195d380)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x19d7b20)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x1a1c150)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x19f52f0)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x19a5720)
kmail(4027) KMReaderWin::event: Entering function e= QChildEvent(ChildAdded, QObject(0x1979ae0)
kmail(4027) KMReaderWin::event: Entering funct...

Created attachment 31063
Trace working with delay and one without that crash

Download full text (35.6 KiB)

Some more useful kDebug to find the cause or mRootNode cause.
I think the interesting part is KMReaderWin::parseMsg: The root node is not yet processed! Danger!
But why is the processing so late and we just left that message and are trying to get back quickly..

OK With wait for message to display
kmail(26104) KMail::MessageListView::Core::View::slotSelectionChanged: Message selected [ Konsultmöte Region Norr ]
kmail(26104) FolderStorage::getMsg: Entering function idx= 1
kmail(26104) FolderStorage::getMsg: setting msg= 0x2ecd2b0
kmail(26104) FolderStorage::unGetMsg: Entering function
kmail(26104) KMMessage::fromStrip: Entering function
kmail(26104) KMMessage::msgId: Entering function this= 0x2ecd2b0 mMsg= 0x2c15900
kmail(26104) KMMessage::~KMMessage: Entering function delete mMsg= 0x2c15900 mFileName= "1233865778.3694.3RbW9:2,S"
kmail(26104) FolderStorage::getMsg: Entering function idx= 0
kmail(26104) KMMessage::KMMessage: Entering function
kmail(26104) KMMessage::init: Entering function aMsg= 0x0
kmail(26104) KMMessage::init: No aMsg so new mMsg= 0x2fec500 aMsg= 0x0
kmail(26104) KMMessage::fromDwString: Entering function aSetStatus= false
kmail(26104) FolderStorage::getMsg: reading msg= 0x2fb6fe0
kmail(26104) KMReaderWin::setMsg: Entering function aMsg= 0x2fb6fe0 force= false
kmail(26104) KMReaderWin::setMsg: ( 1954229106 , last 1954229107 ) "Konsultmöte Region Norr" , readyToShow true
kmail(26104) FolderStorage::getMsg: Entering function idx= 1
kmail(26104) KMMessage::KMMessage: Entering function
kmail(26104) KMMessage::init: Entering function aMsg= 0x0
kmail(26104) KMMessage::init: No aMsg so new mMsg= 0x2336b40 aMsg= 0x0
kmail(26104) KMMessage::fromDwString: Entering function aSetStatus= false
kmail(26104) FolderStorage::getMsg: reading msg= 0x2336a80
kmail(26104) FolderStorage::getMsg: Entering function...

Download full text (8.7 KiB)

Two separate crashes' backtraces listed here:

Crash (A):

Application: KMail (kmail), signal SIGABRT
0x00000033d0ea86e1 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 20465)]

Thread 2 (Thread 0x4225f950 (LWP 20484)):
#0 0x00000033d0edf4b2 in select () from /lib/libc.so.6
#1 0x00000037b7d35006 in ?? () from /usr/lib/libQtCore.so.4
#2 0x00000037b7c6c362 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00000033d1a073ea in start_thread () from /lib/libpthread.so.0
#4 0x00000033d0ee6cbd in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f23ed2a76f0 (LWP 20465)):
[KCrash Handler]
#5 0x00000033d0e33015 in raise () from /lib/libc.so.6
#6 0x00000033d0e34b83 in abort () from /lib/libc.so.6
#7 0x00000037b7c646b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8 0x00000037b7c647fd in qFatal () from /usr/lib/libQtCore.so.4
#9 0x0000003573bff681 in ?? () from /usr/lib/libkmailprivate.so.4
#10 0x0000003573bfe111 in ?? () from /usr/lib/libkmailprivate.so.4
#11 0x0000003573c47fe6 in ?? () from /usr/lib/libkmailprivate.so.4
#12 0x0000003573bfdb99 in ?? () from /usr/lib/libkmailprivate.so.4
#13 0x0000003573df12c6 in ?? () from /usr/lib/libkmailprivate.so.4
#14 0x0000003573df1438 in ?? () from /usr/lib/libkmailprivate.so.4
#15 0x00000037b7d69134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0x00000037b7d63a43 in QObject::event () from /usr/lib/libQtCore.so.4
#17 0x00000037b95cac3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#18 0x00000037b95d29ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0x00000037ef6065db in KApplication::notify (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>)
    at /build/buildd/kde4libs-4.2.0/kdeui/kernel/kapplication.cpp:307
#20 0x00000037b7d54d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#21 0x00000037b7d80ab6 in ?? () from /usr/lib/libQtCore.so.4
#22 0x00000037b7d7d1fd in ?? () from /usr/lib/libQtCore.so.4
#23 0x00000037b7039d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0x00000037b703d50d in ?? () from /usr/lib/libglib-2.0.so.0
#25 0x00000037b703d6cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0x00000037b7d7d15f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#27 0x00000037b965ca6f in ?? () from /usr/lib/libQtGui.so.4
#28 0x00000037b7d53682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#29 0x00000037b7d5380d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#30 0x00000037b7d55cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#31 0x000000000040309b in _start ()

Crash (B):

Application: KMail (kmail), signal SIGABRT
0x00000033d0ea86e1 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 22039)]

Thread 3 (Thread 0x427fe950 (LWP 22082)):
#0 0x00000033d0edf4b2 in select () from /lib/libc.so.6
#1 0x00000037b7d35006 in ?? () from /usr/lib/libQtCore.so.4
#2 0x00000037b7c6c362 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00000033d1a073ea in start_thread () from /lib/libpthread.so.0
#4 0x00000033d0ee6cbd in clone () from /lib/libc.so.6
#5 0x000000000000000...

Read more...

@Ed: your crashes are probably different issues. If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace in a NEW report? You may need to install the debug symbols package for KDEPIM/KMail Thanks :)

*** Bug 185308 has been marked as a duplicate of this bug. ***

Application: KMail (kmail), signal SIGSEGV
0x00000035718a7f81 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7fd63c7fc800 (LWP 7455))]

Thread 2 (Thread 0x7fd62c944950 (LWP 7469)):
#0 0x00000035718deaa2 in select () from /lib64/libc.so.6
#1 0x0000003d5e522626 in ?? () from /usr/lib64/libQtCore.so.4
#2 0x0000003d5e459852 in ?? () from /usr/lib64/libQtCore.so.4
#3 0x00000035724073da in start_thread () from /lib64/libpthread.so.0
#4 0x00000035718e62bd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fd63c7fc800 (LWP 7455)):
[KCrash Handler]
#5 0x0000003d6baa35ef in ?? () from /usr/lib64/libkmailprivate.so.4
#6 0x0000003d6b983cfe in KMMainWidget::updateMessageActions () from /usr/lib64/libkmailprivate.so.4
#7 0x0000003d6b99abd5 in KMMainWidget::qt_metacall () from /usr/lib64/libkmailprivate.so.4
#8 0x0000003d5e556764 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4
#9 0x0000003d5e551073 in QObject::event () from /usr/lib64/libQtCore.so.4
#10 0x0000003d5f1828dd in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4
#11 0x0000003d5f18a68a in QApplication::notify () from /usr/lib64/libQtGui.so.4
#12 0x0000003d60404deb in KApplication::notify () from /usr/lib64/libkdeui.so.5
#13 0x0000003d5e542391 in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4
#14 0x0000003d5e56e0d6 in ?? () from /usr/lib64/libQtCore.so.4
#15 0x0000003d5e56a83d in ?? () from /usr/lib64/libQtCore.so.4
#16 0x0000003d5a43779b in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#17 0x0000003d5a43af6d in ?? () from /lib64/libglib-2.0.so.0
#18 0x0000003d5a43b12b in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#19 0x0000003d5e56a79f in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4
#20 0x0000003d5f21328f in ?? () from /usr/lib64/libQtGui.so.4
#21 0x0000003d5e540cb2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4
#22 0x0000003d5e540e3d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#23 0x0000003d5e5432ed in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4
#24 0x0000000000402b5b in _start ()

On further inspection, it looks like my dump in Comment 19 belongs in bug 41514:
   https://bugs.kde.org/show_bug.cgi?id=41514

Hi
I have just upgraded to Kubuntu jaunty with QT 4.5, KDE 4.2.1 and Kmail 1.11.1 and I'm no longer able to reproduce this bug like I did before.
Also a warning that this is an alpha release and everything is not yet working. http://www.ubuntu.com/testing/jaunty/alpha6

*** Bug 190043 has been marked as a duplicate of this bug. ***

Neal, can you reproduce the crash with KDE >= 4.2.3 ?

*** Bug 201024 has been marked as a duplicate of this bug. ***

Jonathan Thomas (echidnaman) wrote :

Fixed in KDE 4.3.

Changed in kdepim (Ubuntu):
status: Confirmed → Fix Released

*** Bug 202204 has been marked as a duplicate of this bug. ***

*** Bug 205809 has been marked as a duplicate of this bug. ***

*** Bug 206180 has been marked as a duplicate of this bug. ***

Changed in kdepim:
status: Confirmed → Fix Released

*** Bug 207197 has been marked as a duplicate of this bug. ***

*** Bug 208012 has been marked as a duplicate of this bug. ***

*** Bug 208296 has been marked as a duplicate of this bug. ***

*** Bug 208314 has been marked as a duplicate of this bug. ***

*** Bug 208196 has been marked as a duplicate of this bug. ***

*** Bug 209008 has been marked as a duplicate of this bug. ***

Bug 187273 got a new similar crash with different step-cases:

"
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.
"

*** Bug 187273 has been marked as a duplicate of this bug. ***

*** Bug 209254 has been marked as a duplicate of this bug. ***

*** Bug 209913 has been marked as a duplicate of this bug. ***

*** Bug 209704 has been marked as a duplicate of this bug. ***

Updated backtrace from bug 209987:
--

#5 0x0000000000000061 in ?? ()
#6 0x00007f6d891f4f67 in KMReaderWin::parseMsg (this=0xc8ab70, aMsg=0x35aa7f0)
at /usr/src/debug/kdepim-4.3.69svn1027298/kmail/kmreaderwin.cpp:1677
#7 0x00007f6d891ea211 in KMReaderWin::displayMessage (this=0xc8ab70) at
/usr/src/debug/kdepim-4.3.69svn1027298/kmail/kmreaderwin.cpp:1599
#8 0x00007f6d891ea3fe in KMReaderWin::updateReaderWin (this=0xc8ab70) at
/usr/src/debug/kdepim-4.3.69svn1027298/kmail/kmreaderwin.cpp:1542
#9 0x00007f6d891ea96c in KMReaderWin::setMsg (this=0xc8ab70, aMsg=0x35aa7f0,
force=true) at
/usr/src/debug/kdepim-4.3.69svn1027298/kmail/kmreaderwin.cpp:1344
#10 0x00007f6d891e2524 in KMReaderWin::slotMessageArrived (this=0xc8ab70,
msg=0x35aa7f0) at
/usr/src/debug/kdepim-4.3.69svn1027298/kmail/kmreaderwin.cpp:950
#11 0x00007f6d891f8614 in KMReaderWin::qt_metacall (this=0xc8ab70,
_c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff70204f50)
    at /usr/src/debug/kdepim-4.3.69svn1027298/build/kmail/kmreaderwin.moc:200

*** Bug 209987 has been marked as a duplicate of this bug. ***

There appears to be several bugs mentioned in here and I was recommended to become a duplicate of this bug. however, I see what appears to be various bugs lumped in here which makes this bug 180741 only more confusing to figure-out.

My bug 208245 has been narrowed-down to be related with the preview window. If it is enabled, then there is a seg fault, if it is turned-off then kmail operates okay and continues to operate okay.

This question is probably most related with these bug reports:
bug 206180, bug 207197, bug 208296, bug 209008, bug 209704

Question: Are you using the preview window when you reported your bug?
Did your kmail crash if you had the preview window enabled.
Did your kmail continue to work okay if the preview window was off.
If you reported your bug AND you can reproduce the bug with the preview window enabled but cannot reproduce the crash with the preview window turned-off, then you probably have the same bug as bug 208245.

Sorry to bother anybody with this strange question if your bug does not appear related to the preview window. Thanks.

*** Bug 208245 has been marked as a duplicate of this bug. ***

Just want to let you know that with my bug 208245, you can create a crash if you enable preview window in the options, but if you do not enable the preview window, you do not get a crash. I'm guessing this problem is all related to the preview window and whether it is selected or not selected.

With my bug, kmail crashes if you compact a folder and do not switch to another folder within 4-10 seconds: it does not matter whether the preview pane is open or not.

*** Bug 210751 has been marked as a duplicate of this bug. ***

*** Bug 211164 has been marked as a duplicate of this bug. ***

*** Bug 211375 has been marked as a duplicate of this bug. ***

*** Bug 213239 has been marked as a duplicate of this bug. ***

*** Bug 213454 has been marked as a duplicate of this bug. ***

Bug 214112 got another description:
What I was doing when the application crashed:
This is bizarre. I received an email from the Arch Linux mailing list that
somehow triggered kmail to prompt me for my gpg passphrase. The first letter of
the phrase is a 'd' which is also mapped to 'delete message'. When I typed the
'd' into the passphrase box, the message was deleted and kmail crashed and
drkonqi appeared. I'll attach the email if it didn't autoexpunge from the
deleted folder. (If it did, I think I can get a copy from thunderbird)

*** Bug 214112 has been marked as a duplicate of this bug. ***

Hi Dario,
Read comment#41 and comment#43.
Does it crash if you have the preview window open?
Does it crash if you have the preview window closed?
For myself, I was able to narrow my problem down to the preview pane causing the problem.
If it crashes for you regardless of preview pane, you maybe might have a different bug. I'm guessing there are probably 3 different bugs lumped-into this particular bug based on activity that caused crashes.

does anyone know what was the clues that suggested all these bugs are related?

The backtrace of all this crashes are the ~same~ (so they are crashing in the same(or similar) code workflows), suggesting that those reports are in fact related.

*** Bug 214358 has been marked as a duplicate of this bug. ***

*** Bug 210504 has been marked as a duplicate of this bug. ***

*** Bug 221329 has been marked as a duplicate of this bug. ***

LimCore (limcore) wrote :

The same bug strikes again, in Ubuntu 9.10

Same back-trace (parse.. and headers or message body etc).

#5 0x00007fade7ff5900 in DwEntity::Headers() const () from /usr/lib/libmimelib.so.4
#6 0x00007fadeeccd4f0 in KMMessage::headerField (this=0x20d3610, aName=..., encodingMode=KMMessage::MessageCharsetEncoding) at ../../kmail/kmmessage.cpp:1990
#7 0x00007fadeecd0e75 in KMMessage::msgId (this=0x20d3610) at ../../kmail/kmmessage.cpp:1888
#8 0x00007fadeedc7db9 in KMReaderWin::parseMsg (this=0xc98680, aMsg=0x20d3610) at ../../kmail/kmreaderwin.cpp:1758
#9 0x00007fadeedb6eda in KMReaderWin::displayMessage (this=0xc98680) at ../../kmail/kmreaderwin.cpp:1605
#10 0x00007fadeedb70b4 in KMReaderWin::updateReaderWin (this=0xc98680) at ../../kmail/kmreaderwin.cpp:1545
#11 0x00007fadeedc2f9d in KMReaderWin::qt_metacall (this=0xc98680, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff0ed3e730) at ./kmreaderwin.moc:168
#12 0x00007faded9fdddc in QMetaObject::activate (sender=0xc98728, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x1) at kernel/qobject.cpp:3113
#13 0x00007faded9f7d83 in QObject::event (this=0xc98728, e=0x20d3610) at kernel/qobject.cpp:1075
#14 0x00007fadede7befc in QApplicationPrivate::notify_helper (this=0x77c680, receiver=0xc98728, e=0x7fff0ed3ed30) at kernel/qapplication.cpp:4056
#15 0x00007fadede831ce in QApplication::notify (this=0x7fff0ed3f1a0, receiver=0xc98728, e=0x7fff0ed3ed30) at kernel/qapplication.cpp:4021
#16 0x00007fadefc3eab6 in KApplication::notify (this=0x7fff0ed3f1a0, receiver=0xc98728, event=0x7fff0ed3ed30) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x00007faded9e8c2c in QCoreApplication::notifyInternal (this=0x7fff0ed3f1a0, receiver=0xc98728, event=0x7fff0ed3ed30) at kernel/qcoreapplication.cpp:610
#18 0x00007fadeda13862 in QCoreApplication::sendEvent (this=0x77af80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 QTimerInfoList::activateTimers (this=0x77af80) at kernel/qeventdispatcher_unix.cpp:572
#20 0x00007fadeda1125d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#21 0x00007fade4c81bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x00007fade4c85598 in ?? () from /lib/libglib-2.0.so.0
#23 0x00007fade4c856c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x00007fadeda111a6 in QEventDispatcherGlib::processEvents (this=0x743930, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#25 0x00007fadedf104be in QGuiEventDispatcherGlib::processEvents (this=0x2899d, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#26 0x00007faded9e7532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#27 0x00007faded9e7904 in QEventLoop::exec (this=0x7fff0ed3efd0, flags=) at kernel/qeventloop.cpp:201
#28 0x00007faded9e9ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0x0000000000402fe9 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146

Changed in kdepim (Ubuntu):
status: Fix Released → Confirmed

*** Bug 125512 has been marked as a duplicate of this bug. ***

Download full text (3.3 KiB)

Happens still.

Same back trace of the bug - kmail crashes under parseMsg() in parse ID or body(). That bug was makred fixed, but now it happens again, always, in identical conditions, and it crashes in identical way

My recent crash:
[KCrash Handler]
#5 0x00007fade7ff5900 in DwEntity::Headers() const () from /usr/lib/libmimelib.so.4
#6 0x00007fadeeccd4f0 in KMMessage::headerField (this=0x20d3610, aName=..., encodingMode=KMMessage::MessageCharsetEncoding) at ../../kmail/kmmessage.cpp:1990
#7 0x00007fadeecd0e75 in KMMessage::msgId (this=0x20d3610) at ../../kmail/kmmessage.cpp:1888
#8 0x00007fadeedc7db9 in KMReaderWin::parseMsg (this=0xc98680, aMsg=0x20d3610) at ../../kmail/kmreaderwin.cpp:1758
#9 0x00007fadeedb6eda in KMReaderWin::displayMessage (this=0xc98680) at ../../kmail/kmreaderwin.cpp:1605
#10 0x00007fadeedb70b4 in KMReaderWin::updateReaderWin (this=0xc98680) at ../../kmail/kmreaderwin.cpp:1545
#11 0x00007fadeedc2f9d in KMReaderWin::qt_metacall (this=0xc98680, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff0ed3e730) at ./kmreaderwin.moc:168
#12 0x00007faded9fdddc in QMetaObject::activate (sender=0xc98728, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x1) at kernel/qobject.cpp:3113
#13 0x00007faded9f7d83 in QObject::event (this=0xc98728, e=0x20d3610) at kernel/qobject.cpp:1075
#14 0x00007fadede7befc in QApplicationPrivate::notify_helper (this=0x77c680, receiver=0xc98728, e=0x7fff0ed3ed30) at kernel/qapplication.cpp:4056
#15 0x00007fadede831ce in QApplication::notify (this=0x7fff0ed3f1a0, receiver=0xc98728, e=0x7fff0ed3ed30) at kernel/qapplication.cpp:4021
#16 0x00007fadefc3eab6 in KApplication::notify (this=0x7fff0ed3f1a0, receiver=0xc98728, event=0x7fff0ed3ed30) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x00007faded9e8c2c in QCoreApplication::notifyInternal (this=0x7fff0ed3f1a0, receiver=0xc98728, event=0x7fff0ed3ed30) at kernel/qcoreapplication.cpp:610
#18 0x00007fadeda13862 in QCoreApplication::sendEvent (this=0x77af80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 QTimerInfoList::activateTimers (this=0x77af80) at kernel/qeventdispatcher_unix.cpp:572
#20 0x00007fadeda1125d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#21 0x00007fade4c81bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x00007fade4c85598 in ?? () from /lib/libglib-2.0.so.0
#23 0x00007fade4c856c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x00007fadeda111a6 in QEventDispatcherGlib::processEvents (this=0x743930, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#25 0x00007fadedf104be in QGuiEventDispatcherGlib::processEvents (this=0x2899d, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#26 0x00007faded9e7532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#27 0x00007faded9e7904 in QEventLoop::exec (this=0x7fff0ed3efd0, flags=) at kernel/qeventloop.cpp:201
#28 0x00007faded9e9ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0x0000000000402fe9 in main (argc=<value optimized out...

Read more...

Download full text (6.1 KiB)

Ok more information!

The bug appears to be related to some enqueueing of events to main Kmail window while the pin entry is opened.

For some reason, this symptoms appear to show most when using Inbox (I test that on gmail cached/disconnected IMAP).

Reproduce:
1. open kmail, go to inbox of cached imap like gmail
2. select message that is signed+encr
3. pinentyr opens up
4. click a lot in the window of kmail (that is now defocused), like 10 random clicks all over the list of email in that inbox - that list is visible, but it is defocused and is not active (since pinetry is modal)
5. cancel pinentry
6. crash!

Tested on SMP (4 cores).

This got me faster to the bugs we observed, and to some perhaps new bugs - well other bug traces:

You just entered an invalid passphrase.
Do you want to try again, or cancel and view the message undecrypted?

#5 0x0000000002cc5120 in ?? ()
#6 0x00007f90ab8dbc9a in KMReaderWin::parseMsg (this=0x19c3ca0, aMsg=0x2604330) at ../../kmail/kmreaderwin.cpp:1678
#7 0x00007f90ab8caeda in KMReaderWin::displayMessage (this=0x19c3ca0) at ../../kmail/kmreaderwin.cpp:1605
#8 0x00007f90ab8cb0b4 in KMReaderWin::updateReaderWin (this=0x19c3ca0) at ../../kmail/kmreaderwin.cpp:1545

Thread 2 (Thread 0x7f88874d8910 (LWP 2591)):
#0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:220
#1 0x00007f88a7b1d462 in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x2c9aca0, time=30000) at thread/qwaitcondition_unix.cpp:85
#2 QWaitCondition::wait (this=<value optimized out>, mutex=0x2c9aca0, time=30000) at thread/qwaitcondition_unix.cpp:159
#3 0x00007f88a7b134f2 in QThreadPoolThread::run (this=<value optimized out>) at concurrent/qthreadpool.cpp:140
#4 0x00007f88a7b1c445 in QThreadPrivate::start (arg=0x20ef380) at thread/qthread_unix.cpp:188
#5 0x00007f88a2434a04 in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6 0x00007f88a73077bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f88aa4167f0 (LWP 2540)):
[KCrash Handler]
#5 0x0000000002af48f0 in ?? ()
#6 0x00007f88a8fe1c9a in KMReaderWin::parseMsg (this=0x214e6a0, aMsg=0x35846a0) at ../../kmail/kmreaderwin.cpp:1678
#7 0x00007f88a8fd0eda in KMReaderWin::displayMessage (this=0x214e6a0) at ../../kmail/kmreaderwin.cpp:1605
#8 0x00007f88a8fd10b4 in KMReaderWin::updateReaderWin (this=0x214e6a0) at ../../kmail/kmreaderwin.cpp:1545
#9 0x00007f88a8fdcf9d in KMReaderWin::qt_metacall (this=0x214e6a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffeca45fa0) at ./kmreaderwin.moc:168
#10 0x00007f88a7c17ddc in QMetaObject::activate (sender=0x214e748, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x36137d0) at kernel/qobject.cpp:3113
#11 0x00007f88a7c11d83 in QObject::event (this=0x214e748, e=0x46) at kernel/qobject.cpp:1075
#12 0x00007f88a8095efc in QApplicationPrivate::notify_helper (this=0x1c9f1a0, receiver=0x214e748, e=0x7fffeca465a0) at kernel/qapplication.cpp:4056
[...]

Thread 2 (Thread 0x7f99a29fa910 (LWP 2617)):
#0 pthread_cond_timedwait@@GLIBC_2....

Read more...

Kyubutsu (jf) wrote :
Download full text (5.6 KiB)

kubuntu 9.10 x64 on mt3422 laptop
crash reproducible following original poster's steps

backtrace:

Application: KMail (kmail), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5 0x00007fe339047c97 in KMReaderWin::parseMsg (this=0x2633820, aMsg=0x2d2e940) at ../../kmail/kmreaderwin.cpp:1678
#6 0x00007fe339036eda in KMReaderWin::displayMessage (this=0x2633820) at ../../kmail/kmreaderwin.cpp:1605
#7 0x00007fe3390370b4 in KMReaderWin::updateReaderWin (this=0x2633820) at ../../kmail/kmreaderwin.cpp:1545
#8 0x00007fe339041fac in KMReaderWin::setMsg (this=0x2633820, aMsg=0x2d2e940, force=true) at ../../kmail/kmreaderwin.cpp:1347
#9 0x00007fe339042dc4 in KMReaderWin::slotMessageArrived (this=0x2633820, msg=0x2d2e940) at ../../kmail/kmreaderwin.cpp:935
#10 0x00007fe339043164 in KMReaderWin::qt_metacall (this=0x2633820, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1634f9e0) at ./kmreaderwin.moc:196
#11 0x00007fe337c7dddc in QMetaObject::activate (sender=0x2740820, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x2fa3450) at kernel/qobject.cpp:3113
#12 0x00007fe339230d9f in KMail::FolderJob::messageRetrieved (this=0x2d2e940, _t1=0x2d2e940) at ./folderjob.moc:99
#13 0x00007fe33923cc97 in KMail::ImapJob::slotGetMessageResult (this=0x2740820, job=<value optimized out>) at ../../kmail/imapjob.cpp:460
#14 0x00007fe33924104b in KMail::ImapJob::qt_metacall (this=0x2740820, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1634fbe0) at ./imapjob.moc:82
#15 0x00007fe337c7dddc in QMetaObject::activate (sender=0x2617490, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x2fa3450) at kernel/qobject.cpp:3113
#16 0x00007fe339906af2 in KJob::result (this=0x2d2e940, _t1=0x2617490) at ./kjob.moc:188
#17 0x00007fe339906e6f in KJob::emitResult (this=0x2617490) at ../../kdecore/jobs/kjob.cpp:304
#18 0x00007fe331a26d93 in KIO::SimpleJob::slotFinished (this=0x2617490) at ../../kio/kio/job.cpp:477
#19 0x00007fe331a27253 in KIO::TransferJob::slotFinished (this=0x2617490) at ../../kio/kio/job.cpp:948
#20 0x00007fe331a25b61 in KIO::TransferJob::qt_metacall (this=0x2617490, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff16350000) at ./jobclasses.moc:343
#21 0x00007fe337c7dddc in QMetaObject::activate (sender=0x2ea3e80, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x2fa3450) at kernel/qobject.cpp:3113
#22 0x00007fe331ae7a81 in KIO::SlaveInterface::dispatch (this=0x2ea3e80, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#23 0x00007fe331ae4333 in KIO::SlaveInterface::dispatch (this=0x2ea3e80) at ../../kio/kio/slaveinterface.cpp:91
#24 0x00007fe331ad714d in KIO::Slave::gotInput (this=0x2ea3e80) at ../../kio/kio/slave.cpp:322
#25 0x00007fe331ad926c in KIO::Slave::qt_metacall (this=0x2ea3e80, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff163503c0) at ./slave.moc:76
#26 0x00007fe337c7dddc in QMetaObject::activate (sender=0x2c8a8d0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv...

Read more...

Jonathan Thomas (echidnaman) wrote :

Hi there,

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at: http://bugs.kde.org/show_bug.cgi?id=180741
Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.

Thanks!

Changed in kdepim:
status: Fix Released → Unknown
Changed in kdepim (Ubuntu):
status: Confirmed → Invalid

*** Bug 222555 has been marked as a duplicate of this bug. ***

*** Bug 220271 has been marked as a duplicate of this bug. ***

*** Bug 218913 has been marked as a duplicate of this bug. ***

*** Bug 217171 has been marked as a duplicate of this bug. ***

Changed in kdepim:
status: Unknown → Confirmed

*** Bug 225204 has been marked as a duplicate of this bug. ***

*** Bug 222251 has been marked as a duplicate of this bug. ***

*** Bug 221574 has been marked as a duplicate of this bug. ***

*** Bug 221549 has been marked as a duplicate of this bug. ***

*** Bug 240027 has been marked as a duplicate of this bug. ***

*** Bug 218973 has been marked as a duplicate of this bug. ***

*** Bug 235893 has been marked as a duplicate of this bug. ***

*** Bug 212424 has been marked as a duplicate of this bug. ***

*** Bug 240379 has been marked as a duplicate of this bug. ***

*** Bug 218782 has been marked as a duplicate of this bug. ***

*** Bug 254065 has been marked as a duplicate of this bug. ***

*** Bug 230672 has been marked as a duplicate of this bug. ***

*** Bug 215002 has been marked as a duplicate of this bug. ***

Changed in kdepim:
importance: Unknown → High

*** Bug 280389 has been marked as a duplicate of this bug. ***

Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding

Changed in kdepim:
status: Confirmed → Unknown
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.