Version: (using KDE 4.1.3) OS: Linux Installed from: Ubuntu Packages Just launch Kontact, from summary click on a task. Application : Kontact (kontact), signal SIGSEGV (no debugging symbols found) (...) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb4d4b6c0 (LWP 8115)] [New Thread 0xb0ca3b90 (LWP 8146)] (no debugging symbols found) (...) (no debugging symbols found) [KCrash handler] #6 0xb7e38b26 in qHash () from /usr/lib/libQtCore.so.4 #7 0xb56c3cbf in ?? () from /usr/lib/libkcal.so.4 #8 0xb56beaba in KCal::CalendarLocal::event () from /usr/lib/libkcal.so.4 #9 0xb570e2d7 in KCal::ResourceCached::event () from /usr/lib/libkcal.so.4 #10 0xb571cc22 in KCal::CalendarResources::event () from /usr/lib/libkcal.so.4 #11 0xb56b633e in KCal::Calendar::incidence () from /usr/lib/libkcal.so.4 #12 0xb01dc0cb in CalendarView::editIncidence () from /usr/lib/libkorganizerprivate.so.4 #13 0xb025af07 in ActionManager::editIncidence () from /usr/lib/libkorganizerprivate.so.4 #14 0xb027c8c7 in KOrganizerIfaceImpl::editIncidence () from /usr/lib/libkorganizerprivate.so.4 #15 0xb02be958 in ?? () from /usr/lib/libkorganizerprivate.so.4 #16 0xb690926e in ?? () from /usr/lib/libQtDBus.so.4 #17 0xb690a4a7 in ?? () from /usr/lib/libQtDBus.so.4 #18 0xb690a9b1 in ?? () from /usr/lib/libQtDBus.so.4 #19 0xb690b527 in ?? () from /usr/lib/libQtDBus.so.4 #20 0xb690bb4a in ?? () from /usr/lib/libQtDBus.so.4 #21 0xb690be09 in ?? () from /usr/lib/libQtDBus.so.4 #22 0xb690db9f in ?? () from /usr/lib/libQtDBus.so.4 #23 0xb68f7a31 in QDBusConnection::call () from /usr/lib/libQtDBus.so.4 #24 0xb6916dab in QDBusAbstractInterface::callWithArgumentList () from /usr/lib/libQtDBus.so.4 #25 0xb1c08639 in ?? () from /usr/lib/kde4/kontact_todoplugin.so #26 0xb1c0b8b5 in ?? () from /usr/lib/kde4/kontact_todoplugin.so #27 0xb7f1ca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #28 0xb7f1d7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #29 0xb7b15653 in KUrlLabel::leftClickedUrl () from /usr/lib/libkdeui.so.5 #30 0xb7b16232 in KUrlLabel::mouseReleaseEvent () from /usr/lib/libkdeui.so.5 #31 0xb6f66962 in QWidget::event () from /usr/lib/libQtGui.so.4 #32 0xb729dfd3 in QFrame::event () from /usr/lib/libQtGui.so.4 #33 0xb72a3579 in QLabel::event () from /usr/lib/libQtGui.so.4 #34 0xb7b16067 in KUrlLabel::event () from /usr/lib/libkdeui.so.5 #35 0xb6f0e8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #36 0xb6f170e1 in QApplication::notify () from /usr/lib/libQtGui.so.4 #37 0xb7a09b2d in KApplication::notify () from /usr/lib/libkdeui.so.5 #38 0xb7f07e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #39 0xb6f1636e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #40 0xb6f80656 in ?? () from /usr/lib/libQtGui.so.4 #41 0xb6f7f9e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #42 0xb6fa97aa in ?? () from /usr/lib/libQtGui.so.4 #43 0xb6ae36f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #44 0xb6ae6da3 in ?? () from /usr/lib/libglib-2.0.so.0 #45 0xb6ae6f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #46 0xb7f32478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #47 0xb6fa8ea5 in ?? () from /usr/lib/libQtGui.so.4 #48 0xb7f0652a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #49 0xb7f066ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #50 0xb7f08da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #51 0xb6f0e767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #52 0x0804bf52 in _start () #0 0xb8024430 in __kernel_vsyscall ()
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 here? Thanks :) 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 here? Thanks :)
No news from the bug reporter, marking as REMIND. Please reopen this bug report if you experience the same bug again.
*** This bug has been marked as a duplicate of bug 184883 ***