marking a recurring kontact to-do as complete causes application crash

Does this crash still occur for you in newer versions of kontact? I tried to reproduce this behaviour on intrepid with kontact 1.3 and it doesn't seem to crash from me. If you are still seeing this crash could you tell us in what version of Kontact/KDE.

If the crash does occur could you try to provide a backtrace from the crash. Ideally with the package kdepim-dbg installed to provide debugging symbols

The latest version of Kontact in hardy is 1.2.9 (at least that's what my system says).

Running KDE 3.5.10.

I just tested, and this crash still occurs.

I now have the KDE debugging libraries loaded, and this is the backtrace I received:

----

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f2e989e06f0 (LWP 7689)]
[KCrash handler]
#5 0x00007f2e8b7e3886 in KOTodoView::processDelayedNewPercentage ()
   from /usr/lib/libkorganizer.so.1
#6 0x00007f2e8b7e5038 in KOTodoView::qt_invoke ()
   from /usr/lib/libkorganizer.so.1
#7 0x00007f2e92a7cfd0 in QObject::activate_signal (this=0x84d040,
    clist=0xd72ad0, o=0x7fffa0a1a950) at kernel/qobject.cpp:2359
#8 0x00007f2e92df5181 in QSignal::signal (this=0x84d040, t0=@0x84d090)
    at .moc/debug-shared-mt/moc_qsignal.cpp:100
#9 0x00007f2e92a9b1a3 in QSignal::activate (this=0x84d040)
    at kernel/qsignal.cpp:215
#10 0x00007f2e92aa29e4 in QSingleShotTimer::event (this=0x84cff0)
    at kernel/qtimer.cpp:289
#11 0x00007f2e92a1533a in QApplication::internalNotify (this=0x7fffa0a1b2a0,
    receiver=0x84cff0, e=0x7fffa0a1adf0) at kernel/qapplication.cpp:2638
#12 0x00007f2e92a17093 in QApplication::notify (this=0x7fffa0a1b2a0,
    receiver=0x84cff0, e=0x7fffa0a1adf0) at kernel/qapplication.cpp:2361
#13 0x00007f2e9414b6bd in KApplication::notify (this=0x7fffa0a1b2a0,
    receiver=0x84cff0, event=0x7fffa0a1adf0)
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#14 0x00007f2e929a620e in QApplication::sendEvent (receiver=0x84cff0,
    event=0x7fffa0a1adf0) at ../include/qapplication.h:523
#15 0x00007f2e92a08abc in QEventLoop::activateTimers (this=0x6a1040)
    at kernel/qeventloop_unix.cpp:559
#16 0x00007f2e929bb107 in QEventLoop::processEvents (this=0x6a1040, flags=4)
    at kernel/qeventloop_x11.cpp:392
#17 0x00007f2e92a2f5bf in QEventLoop::enterLoop (this=0x6a1040)
    at kernel/qeventloop.cpp:201
#18 0x00007f2e92a2f2ab in QEventLoop::exec (this=0x6a1040)
    at kernel/qeventloop.cpp:148
#19 0x00007f2e92a16e00 in QApplication::exec (this=0x7fffa0a1b2a0)
    at kernel/qapplication.cpp:2761
#20 0x0000000000419299 in ?? ()
#21 0x00007f2e8f2441c4 in __libc_start_main () from /lib/libc.so.6
#22 0x0000000000418a59 in ?? ()
#23 0x00007fffa0a1b578 in ?? ()
#24 0x0000000000000000 in ?? ()

----

Thanks for following up.

Not triaged.
Please install kdepim-dbg and get a new backtrace, the current one is useable becuase the debug symbols are missing.

Also, the status of this in the KDE 4 version of KOrganizer would be very appreciated.

With the debugging library enabled, I get a crash the instant that I try to save a calendar containing a recurring to-do; so I'm not sure whether this is the same bug or another one. I have tried to save the calendar several times, and this happens each time:

----

[Thread debugging using libthread_db enabled]
[New Thread 0x7f25696ed6f0 (LWP 18943)]
[KCrash handler]
#5 0x00007f255c4cb27e in KOAgendaItem::paintEvent (this=0x11cbec0,
    ev=0x7fff71728690)
    at /build/buildd/kdepim-3.5.10/./korganizer/koagendaitem.cpp:753
#6 0x00007f25637be858 in QWidget::event (this=0x11cbec0, e=0x7fff71728690)
    at kernel/qwidget.cpp:4808
#7 0x00007f256372233a in QApplication::internalNotify (this=0x7fff71728ed0,
    receiver=0x11cbec0, e=0x7fff71728690) at kernel/qapplication.cpp:2638
#8 0x00007f2563724be3 in QApplication::notify (this=0x7fff71728ed0,
    receiver=0x11cbec0, e=0x7fff71728690) at kernel/qapplication.cpp:2526
#9 0x00007f2564e586bd in KApplication::notify (this=0x7fff71728ed0,
    receiver=0x11cbec0, event=0x7fff71728690)
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#10 0x00007f25636b3280 in QApplication::sendSpontaneousEvent (
    receiver=0x11cbec0, event=0x7fff71728690) at kernel/qapplication.h:526
#11 0x00007f25636a2a7c in QETWidget::translatePaintEvent (this=0x11cbec0,
    event=0x7fff71728c20) at kernel/qapplication_x11.cpp:5787
#12 0x00007f25636b00f6 in QApplication::x11ProcessEvent (this=0x7fff71728ed0,
    event=0x7fff71728c20) at kernel/qapplication_x11.cpp:3505
#13 0x00007f25636c7106 in QEventLoop::processEvents (this=0x6a10f0, flags=4)
    at kernel/qeventloop_x11.cpp:195
#14 0x00007f256373c5bf in QEventLoop::enterLoop (this=0x6a10f0)
    at kernel/qeventloop.cpp:201
#15 0x00007f256373c2ab in QEventLoop::exec (this=0x6a10f0)
    at kernel/qeventloop.cpp:148
#16 0x00007f2563723e00 in QApplication::exec (this=0x7fff71728ed0)
    at kernel/qapplication.cpp:2761
#17 0x0000000000419299 in main (argc=<value optimized out>,
    argv=<value optimized out>)
    at /build/buildd/kdepim-3.5.10/./kontact/src/main.cpp:163

----

I have no idea what happens with KDE4.

argh! korganizer is now crashing every time I start it.

I have no idea how to make it usable again. All I did was to load the debugging symbols and to trigger this bug :-(

This is the backtrace I am getting:

[Thread debugging using libthread_db enabled]
[New Thread 0x7f46f924e6f0 (LWP 22124)]
[KCrash handler]
#5 0x00007f46ec02355d in KOAgenda::setNoActionCursor (this=0xd21700,
    moveItem=0xed48b0, viewportPos=<value optimized out>)
    at /build/buildd/kdepim-3.5.10/./korganizer/koagenda.cpp:1192
#6 0x00007f46ec028b51 in KOAgenda::eventFilter_mouse (this=0xd21700,
    object=0xed48b0, me=<value optimized out>)
    at /build/buildd/kdepim-3.5.10/./korganizer/koagenda.cpp:651
#7 0x00007f46ec022838 in KOAgenda::eventFilter (this=0xd21700,
    object=0xed48b0, event=0x7fff01288050)
    at /build/buildd/kdepim-3.5.10/./korganizer/koagenda.cpp:355
#8 0x00007f46f32e8f6f in QObject::activate_filters (this=0xed48b0,
    e=0x7fff01288050) at kernel/qobject.cpp:906
#9 0x00007f46f32e8fe8 in QObject::event (this=0xed48b0, e=0x7fff01288050)
    at kernel/qobject.cpp:738
#10 0x00007f46f331f2bb in QWidget::event (this=0xed48b0, e=0x7fff01288050)
    at kernel/qwidget.cpp:4681
#11 0x00007f46f328333a in QApplication::internalNotify (this=0x7fff01288970,
    receiver=0xed48b0, e=0x7fff01288050) at kernel/qapplication.cpp:2638
#12 0x00007f46f3285410 in QApplication::notify (this=0x7fff01288970,
    receiver=0xed48b0, e=0x7fff01288050) at kernel/qapplication.cpp:2424
#13 0x00007f46f49b96bd in KApplication::notify (this=0x7fff01288970,
    receiver=0xed48b0, event=0x7fff01288050)
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#14 0x00007f46f3214280 in QApplication::sendSpontaneousEvent (
    receiver=0xed48b0, event=0x7fff01288050) at kernel/qapplication.h:526
#15 0x00007f46f3212e94 in QETWidget::translateMouseEvent (this=0xed48b0,
    event=0x7fff012886c0) at kernel/qapplication_x11.cpp:4306
#16 0x00007f46f3211060 in QApplication::x11ProcessEvent (this=0x7fff01288970,
    event=0x7fff012886c0) at kernel/qapplication_x11.cpp:3483
#17 0x00007f46f3228106 in QEventLoop::processEvents (this=0x6a10f0, flags=4)
    at kernel/qeventloop_x11.cpp:195
#18 0x00007f46f329d5bf in QEventLoop::enterLoop (this=0x6a10f0)
    at kernel/qeventloop.cpp:201
#19 0x00007f46f329d2ab in QEventLoop::exec (this=0x6a10f0)
    at kernel/qeventloop.cpp:148
#20 0x00007f46f3284e00 in QApplication::exec (this=0x7fff01288970)
    at kernel/qapplication.cpp:2761
#21 0x0000000000419299 in main (argc=<value optimized out>,
    argv=<value optimized out>)
    at /build/buildd/kdepim-3.5.10/./kontact/src/main.cpp:163

This bug should be frowarded to http://bugs.kde.org

The new crash you experience is not related to the original bug. Please see bug 286905 for progress regarding the new crash.

Closing as per upstream indication in the KDE bug.