Version: 1.2.3 (using KDE KDE 3.5.4) Installed from: SuSE RPMs I created a korganizer entry by dragging a mail message onto "Calendar" icon in Kontact. Then I selected the added task in Calendar. In the task summary (shown on the left side) there was an entry: "1 attachment: Show mail", "Show mail" being clickable. When I clicked on "Show mail", kontact crashed. Then the following text was in the console: ----------------------------------- QObject::connect: No such slot KMReaderMainWin::slotForwardMsg() QObject::connect: (sender name: 'message_forward') QObject::connect: (receiver name: 'readerwindow#1') *** KMail got signal 11 (Crashing) KCrash: Application 'kontact' crashing... ----------------------------------- Backtrace: ----------------------------------- Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1241250128 (LWP 4963)] [New Thread -1281201248 (LWP 4967)] [New Thread -1272808544 (LWP 4966)] [New Thread -1264415840 (LWP 4965)] [New Thread -1256023136 (LWP 4964)] [KCrash handler] #6 0xb569608a in KMMsgBase::assign () from /opt/kde3/lib/libkmailprivate.so #7 0xb569611f in KMMsgBase::KMMsgBase () from /opt/kde3/lib/libkmailprivate.so #8 0xb55595cf in KMMessage::KMMessage () from /opt/kde3/lib/libkmailprivate.so #9 0xb56fdd7f in KMKernel::showMail () from /opt/kde3/lib/libkmailprivate.so #10 0xb5703ade in KMailIface::process () from /opt/kde3/lib/libkmailprivate.so #11 0xb70cae87 in DCOPClient::receive () from /opt/kde3/lib/libDCOP.so.4 #12 0xb70cd07d in DCOPClient::call () from /opt/kde3/lib/libDCOP.so.4 #13 0xb70cd1b7 in DCOPClient::call () from /opt/kde3/lib/libDCOP.so.4 #14 0xb2b96745 in KMailIface_stub::showMail () from /opt/kde3/lib/libkorganizer_eventviewer.so.1 #15 0xb2b9385b in UriHandler::process () from /opt/kde3/lib/libkorganizer_eventviewer.so.1 #16 0xb2b92dcd in KOEventViewer::setSource () from /opt/kde3/lib/libkorganizer_eventviewer.so.1 #17 0xb6d8fa41 in QTextBrowser::emitLinkClicked () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0xb6dab4dc in QTextEdit::contentsMouseReleaseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #19 0xb6d53365 in QScrollView::viewportMouseReleaseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0xb6d5076f in QScrollView::eventFilter () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0xb6da6747 in QTextEdit::eventFilter () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb6c3b7dc in QObject::activate_filters () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0xb6c3b84b in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0xb6c7488c in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #25 0xb6bdcec7 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #26 0xb6bdddfb in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #27 0xb7298963 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #28 0xb6b7cdd2 in QETWidget::translateMouseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb6b7bfa6 in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0xb6b8c5ea in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #31 0xb6bf3ce8 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #32 0xb6bf3b7e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #33 0xb6bdca7f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #34 0x08058c02 in main () -----------------------------------
Same problem with 1.2.3 in KDE 3.5.5 Same Backtrace
Can't crash it, but clicking on the link seems to trigger a mail check. It's a kmail bug, though.
107823 is related
*** Bug 137355 has been marked as a duplicate of this bug. ***
Same problem but with to-do's as well as celender. Create a new todo item by dragging an email from your inbox in kmail onto the to-do icon in the left handside navigation bar. Then goto todo section and select the todo item that was created. In the view windows (on the left under the calender), select "Show Mail". Kontact then crashes KDE 3.5.5-0.2.fc6 Fedora Core 6 Kontact Container Version 1.2.3 KMail Version 1.9.5 KOrganizer Version 3.5.5
Could #Bug 111217 be related as well?
>Could #Bug 111217 be related as well? No, that is a different backtrace.
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