Version: (using KDE 4.1.3) OS: Linux Installed from: Ubuntu Packages In my task list, I have a task with one subtask. If I click the completed checkbox, kontact crashes reprodicibly. It doesn't matter whether it is marked as complete or not beforehand, or how the subtask is marked. After I restart kontact, the change I made before the crash is reflected in the task list. The task list in question resides in an IMAP mailbox.
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.
Sorry for not reacting, I misunderstood the request email from January. I can confirm that the bug still exists. I can also confirm that it occurs only with IMAP-Resources. On a local resource, I can mark tasks without crash. An additional fact: i'm using the German language version, and the imap resource is set to German as well (apparently, the IMAP folders can be named in the respective language). Below is the backtrace as reported by the KDE crash manager. Let me know if I can be of further assistance. Regards, Luca Anwendung: Kontact (kontact), Signal SIGSEGV 0x00007f459cc296b0 in __nanosleep_nocancel () from /lib/libc.so.6 Thread 1 (Thread 0x7f459f54e6f0 (LWP 26573)): [KCrash Handler] #5 KCal::Incidence::relatedTo (this=0x45474155474e414c) at /build/buildd/kdepimlibs-4.1.4/kcal/incidence.cpp:498 #6 0x00007f4584834e97 in KOTodoModel::moveIfParentChanged (this=0x34d4ea0, curNode=0x3dc4720, todo=0x45474155474e414c, addParentIfMissing=true) at /build/buildd/kdepim-4.1.4/korganizer/views/todoview/kotodomodel.cpp:377 #7 0x00007f4584837935 in KOTodoModel::reloadTodos (this=0x34d4ea0) at /build/buildd/kdepim-4.1.4/korganizer/views/todoview/kotodomodel.cpp:254 #8 0x00007f4584849190 in CalendarView::updateView (this=0x3435840, start=@0x3e9cdd8, end=@0x3e9ce08, updateTodos=76) at /build/buildd/kdepim-4.1.4/korganizer/calendarview.cpp:803 #9 0x00007f4584849f37 in CalendarView::updateView (this=0x3435840) at /build/buildd/kdepim-4.1.4/korganizer/calendarview.cpp:814 #10 0x00007f45848546ec in CalendarView::slotCalendarChanged (this=0x3435840) at /build/buildd/kdepim-4.1.4/korganizer/calendarview.cpp:2271 #11 0x00007f458485910e in CalendarView::qt_metacall (this=0x3435840, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa759cc00) at /build/buildd/kdepim-4.1.4/obj-x86_64-linux-gnu/korganizer/calendarview.moc:559 #12 0x00007f459debd134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0x00007f459a4451ad in KCal::Calendar::qt_metacall (this=0x353cdc0, _c=QMetaObject::InvokeMetaMethod, _id=6644797, _a=<value optimized out>) at /build/buildd/kdepimlibs-4.1.4/obj-x86_64-linux-gnu/kcal/calendar.moc:72 #14 0x00007f459a49e4f5 in KCal::CalendarResources::qt_metacall (this=0x45474155474e414c, _c=55398048, _id=64767776, _a=0x45474155474e414c) at /build/buildd/kdepimlibs-4.1.4/obj-x86_64-linux-gnu/kcal/calendarresources.moc:75 #15 0x00007f459debd134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0x00007f459a48eb6f in KCal::ResourceCalendar::resourceChanged (this=0x45474155474e414c, _t1=0x3550d00) at /build/buildd/kdepimlibs-4.1.4/obj-x86_64-linux-gnu/kcal/resourcecalendar.moc:115 #17 0x00007f4582dc596e in KCal::ResourceKolab::slotEmitResourceChanged (this=0x3550d00) at /build/buildd/kdepim-4.1.4/kresources/kolab/kcal/resourcekolab.cpp:1094 #18 0x00007f4582dc5a35 in KCal::ResourceKolab::qt_metacall (this=0x3550d00, _c=QMetaObject::InvokeMetaMethod, _id=6644797, _a=<value optimized out>) at /build/buildd/kdepim-4.1.4/obj-x86_64-linux-gnu/kresources/kolab/kcal/resourcekolab.moc:76 #19 0x00007f459debd134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #20 0x00007f459deb7a43 in QObject::event () from /usr/lib/libQtCore.so.4 #21 0x00007f459d3cac3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #22 0x00007f459d3d29ba in QApplication::notify () from /usr/lib/libQtGui.so.4 #23 0x00007f459e80613b in KApplication::notify (this=0x7fffa759d890, receiver=0x3550dc0, event=0x7fffa759d540) at /build/buildd/kde4libs-4.1.4/kdeui/kernel/kapplication.cpp:311 #24 0x00007f459dea8d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #25 0x00007f459ded4ab6 in ?? () from /usr/lib/libQtCore.so.4 #26 0x00007f459ded11fd in ?? () from /usr/lib/libQtCore.so.4 #27 0x00007f45975d6d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #28 0x00007f45975da50d in ?? () from /usr/lib/libglib-2.0.so.0 #29 0x00007f45975da6cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #30 0x00007f459ded115f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #31 0x00007f459d45ca6f in ?? () from /usr/lib/libQtGui.so.4 #32 0x00007f459dea7682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #33 0x00007f459dea780d in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #34 0x00007f459dea9cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #35 0x00000000004048e5 in main (argc=1, argv=0x7fffa759df78) at /build/buildd/kdepim-4.1.4/kontact/src/main.cpp:218
The backtrace looks like the one in bug 174894 ( that should be fixed ) If you update to 4.2 try if you can reproduce it too. VERIFIED resolution state is used after the bug is fixed (and that fix is verified), I'm going to reopen the report :)
The kolab resource was rewritten and we're using KCalCore instead of KCal. No use to keep this bug open anymore.