[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#29997: todo purge completed crashes
From:       tdv2847 () cs ! rit ! edu
Date:       2002-04-01 6:31:33
[Download RAW message or body]

Version: 2.99 (3.0rc3) (using KDE 3.0.0 )
Installed from:    Compiled From Sources
Compiler:          2.95.4
OS:                Linux
OS/Compiler notes: Not Specified

I feel this could add valuable information to this bug....here's how you reproduce a \
todo crash in korganizer: 1. create a todo item.. a
2. create a subtodo item below a, a1
3. create another subtodo item below a, a2
4. set a to completed.
5. Now run purge completed.

It has crashed korganizer every time I tried that test on 3.0 rc3.  Crashes even if \
an todo below a like s1 is completed too...but not if there is only one sub item (if \
all sub todo's are completed, it's ok).

I think it might be best to automatically mark all subtodo as completed if the user \
mark the top level todo as completed (or at least display a dialog asking for that).

Backtraces:
[New Thread 1024 (LWP 2942)]
0x41694b79 in wait4 () from /lib/libc.so.6
#0  0x41694b79 in wait4 () from /lib/libc.so.6
#1  0x4170d068 in __check_rhosts_file () from /lib/libc.so.6
#2  0x41556263 in waitpid () from /lib/libpthread.so.0
#3  0x4092910f in KCrash::defaultCrashHandler (sig=6) at kcrash.cpp:224
#4  0x41553d94 in pthread_sighandler () from /lib/libpthread.so.0
#5  0x4161d928 in sigaction () from /lib/libc.so.6
#6  0x4155416d in raise () from /lib/libpthread.so.0
#7  0x4161ee51 in abort () from /lib/libc.so.6
#8  0x415a78f8 in __terminate () from /usr/lib/libstdc++-libc6.2-2.so.3
#9  0x415a7915 in __terminate () from /usr/lib/libstdc++-libc6.2-2.so.3
#10 0x402798ab in __pure_virtual () from /usr/local/kde3/lib/libvcard.so.0
#11 0x400af1f1 in KOTodoView::insertTodoItem (this=0x811c990, todo=0x82d3c48)
    at kotodoview.cpp:352
#12 0x400af056 in KOTodoView::updateView (this=0x811c990) at kotodoview.cpp:325
#13 0x400b027a in KOTodoView::purgeCompleted (this=0x811c990)
    at kotodoview.cpp:487
#14 0x400ad67c in KOTodoView::qt_invoke (this=0x811c990, _id=61, _o=0xbffff2b0)
    at kotodoview.moc:332
#15 0x40d57df2 in QObject::activate_signal (this=0x81254c8, clist=0x8125590, 
    o=0xbffff2b0) at kernel/qobject.cpp:2015
#16 0x410d6590 in QSignal::signal (this=0x81254c8, t0=@0x81254f0)
    at .moc/debug-mt/moc_qsignal.cpp:99
#17 0x40d7939c in QSignal::activate (this=0x81254c8) at kernel/qsignal.cpp:201
#18 0x40e7f7af in QPopupMenu::mouseReleaseEvent (this=0x8123c40, e=0xbffff6f4)
    at widgets/qpopupmenu.cpp:1442
#19 0x40d9aca4 in QWidget::event (this=0x8123c40, e=0xbffff6f4)
    at kernel/qwidget.cpp:4138
#20 0x40ce24a8 in QApplication::internalNotify (this=0xbffffa50, 
    receiver=0x8123c40, e=0xbffff6f4) at kernel/qapplication.cpp:2271
#21 0x40ce1813 in QApplication::notify (this=0xbffffa50, receiver=0x8123c40, 
    e=0xbffff6f4) at kernel/qapplication.cpp:2113
#22 0x408764e4 in KApplication::notify (this=0xbffffa50, receiver=0x8123c40, 
    event=0xbffff6f4) at kapplication.cpp:551
#23 0x410cd354 in QApplication::sendSpontaneousEvent (receiver=0x8123c40, 
    event=0xbffff6f4) at .moc/debug-mt/../../kernel/qapplication.h:455
#24 0x40c6de2c in QETWidget::translateMouseEvent (this=0x8123c40, 
    event=0xbffff95c) at kernel/qapplication_x11.cpp:4760
#25 0x40c6a8d0 in QApplication::x11ProcessEvent (this=0xbffffa50, 
    event=0xbffff95c) at kernel/qapplication_x11.cpp:3618
#26 0x40c69459 in QApplication::processNextEvent (this=0xbffffa50, 
    canWait=true) at kernel/qapplication_x11.cpp:3126
#27 0x40ce47e4 in QApplication::enter_loop (this=0xbffffa50)
    at kernel/qapplication.cpp:3143
#28 0x40c69357 in QApplication::exec (this=0xbffffa50)
    at kernel/qapplication_x11.cpp:3082
#29 0x08048f2f in main (argc=1, argv=0xbffffbd4) at main.cpp:91
#30 0x4160d6cf in __libc_start_main () from /lib/libc.so.6

(Submitted via bugs.kde.org)


[prev in list] [next in list] [prev in thread] [next in thread]