Version: (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages When starting kmail on KDE4.2 beta it didn't work at all. It just crashed on startup. Since the official KDE4.2 release kmail will start up but often crashes on selecting certain messages (on an IMAP-server). It is often a reproducable crash (clicking that same mail again makes kmail crash again as well) but when I select another message first and then the one that made kmail crash, it does work and I can read the message. This has happened to me on multiple occasions. I didn't pay enough attention to be sure, but I think they were all HTML messages. I can't reproduce it at this moment I'm afraid. Here is the debug-thingy: Programma: KMail (kmail), signaal SIGSEGV Thread 1 (Thread 0xb3e9b6c0 (LWP 6860)): [KCrash Handler] #6 0xb5fd0ab5 in QCoreApplication::postEvent () from /usr/lib/libQtCore.so.4 #7 0xb5fd0d9c in QCoreApplication::postEvent () from /usr/lib/libQtCore.so.4 #8 0xb5fdf467 in QObject::deleteLater () from /usr/lib/libQtCore.so.4 #9 0xb75a16d2 in ?? () from /usr/lib/libkmailprivate.so.4 #10 0xb75a61c4 in ?? () from /usr/lib/libkmailprivate.so.4 #11 0xb5fe5a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb5fe67e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0xb7a4e8b3 in KJob::result () from /usr/lib/libkdecore.so.5 #14 0xb7a4ed59 in KJob::emitResult () from /usr/lib/libkdecore.so.5 #15 0xb6c793b5 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.5 #16 0xb6c7a623 in KIO::TransferJob::slotFinished () from /usr/lib/libkio.so.5 #17 0xb6c7b70b in KIO::TransferJob::qt_metacall () from /usr/lib/libkio.so.5 #18 0xb5fe5a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #19 0xb5fe67e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #20 0xb6d366a7 in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.5 #21 0xb6d3a3e7 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #22 0xb6d36b87 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #23 0xb6d26f4d in KIO::Slave::gotInput () from /usr/lib/libkio.so.5 #24 0xb6d294a3 in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5 #25 0xb5fe5a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #26 0xb5fe67e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #27 0xb6c3fbe7 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5 #28 0xb6c41553 in ?? () from /usr/lib/libkio.so.5 #29 0xb6c41936 in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5 #30 0xb5fdebfb in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4 #31 0xb5fe0771 in QObject::event () from /usr/lib/libQtCore.so.4 #32 0xb62618ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #33 0xb626972e in QApplication::notify () from /usr/lib/libQtGui.so.4 #34 0xb7d60fed in KApplication::notify () from /usr/lib/libkdeui.so.5 #35 0xb5fd0e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #36 0xb5fd1ae5 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #37 0xb5fd1cdd in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #38 0xb5ffb82f in ?? () from /usr/lib/libQtCore.so.4 #39 0xb461a6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #40 0xb461dda3 in ?? () from /usr/lib/libglib-2.0.so.0 #41 0xb461df61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #42 0xb5ffb478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #43 0xb62fbea5 in ?? () from /usr/lib/libQtGui.so.4 #44 0xb5fcf52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #45 0xb5fcf6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #46 0xb5fd1da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #47 0xb6261767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #48 0x0804a7a0 in _start ()
Thank you for your report. Unfortunately, your backtrace is not helpful. As you can reproduce this crash, could you please install the debug package and provide a better one ? You will find more informations on this page : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Hi Christophe, I would like to, but the bug seems to have been resolved since kmail usually doesn't crash anymore after an apt-get upgrade around mid february. It sometimes still does, but that's so rare that I can't give much more useful input anymore. Thanks for attending though. I put the status to resolved.