Bug 136667 - Korganizer crashed while marking "to-do" items as done.
Summary: Korganizer crashed while marking "to-do" items as done.
Status: RESOLVED WORKSFORME
Alias: None
Product: korganizer
Classification: Applications
Component: todoview (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 137584 191470 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-11-01 20:36 UTC by Tobias Ussing
Modified: 2010-03-28 20:40 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Ussing 2006-11-01 20:36:01 UTC
Version:           svn 301036 (using KDE Devel)
Installed from:    Compiled sources
Compiler:          i686-pc-linux-gnu-3.4.6 
OS:                Linux

I had a daily occurring to-do, which i hadn't marked done for a few days. I clicked done on it a few times(didn't really count). It reached one that wasn't red(wasn't overdue), i clicked on that one either once or twice, and korganizer crashed with the following backtrace.

I tried to provoke a crash again, but i didn't succeed. 

I will let it get a backlog again, and do the same next week to see if i can provoke it to crash again.

Sincerely
Tobias

------------


Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1245325648 (LWP 13983)]
[New Thread -1376818272 (LWP 9465)]
[New Thread -1368425568 (LWP 9464)]
[New Thread -1360032864 (LWP 9463)]
[New Thread -1351640160 (LWP 9462)]
[New Thread -1343247456 (LWP 9461)]
[New Thread -1334854752 (LWP 9460)]
[New Thread -1326462048 (LWP 9459)]
[New Thread -1318069344 (LWP 9458)]
[New Thread -1309676640 (LWP 9457)]
[New Thread -1301283936 (LWP 9456)]
[New Thread -1283097696 (LWP 14015)]
[New Thread -1274704992 (LWP 14014)]
[New Thread -1266312288 (LWP 14013)]
[New Thread -1257919584 (LWP 14012)]
[KCrash handler]
#5  0xb7dc5f55 in KCal::IncidenceBase::isReadOnly (this=0x39f)
    at incidencebase.h:127
#6  0xb2b6a0dc in KOTodoView::processDelayedNewPercentage (this=0x885c2f0)
    at kotodoview.cpp:1023
#7  0xb2b6e30c in KOTodoView::qt_invoke (this=0x885c2f0, _id=142983920, 
    _o=0xbfd66c10) at kotodoview.moc:341
#8  0xb646be88 in QObject::activate_signal (this=0x81ff428, clist=0x8582520, 
    o=0xbfd66c10) at qobject.cpp:2356
#9  0xb68544ad in QSignal::signal (this=0x81ff428, t0=@0x81ff450)
    at moc_qsignal.cpp:100
#10 0xb648e067 in QSignal::activate (this=0x81ff428) at qsignal.cpp:212
#11 0xb6498144 in QSingleShotTimer::event (this=0x81ff400) at qtimer.cpp:286
#12 0xb63faca1 in QApplication::internalNotify (this=0xbfd67210, 
    receiver=0x81ff400, e=0xbfd66f70) at qapplication.cpp:2635
#13 0xb63f9ef0 in QApplication::notify (this=0xbfd67210, receiver=0x81ff400, 
    e=0xbfd66f70) at qapplication.cpp:2358
#14 0xb6c6fa7a in KApplication::notify (this=0xbfd67210, receiver=0x81ff400, 
    event=0xbfd66f70) at kapplication.cpp:550
#15 0xb7884b00 in QApplication::sendEvent (receiver=0x931c078, event=0x931c078)
    at qapplication.h:496
#16 0xb63e61ff in QEventLoop::activateTimers (this=0x8139f20)
    at qeventloop_unix.cpp:556
#17 0xb6395e26 in QEventLoop::processEvents (this=0x8139f20, flags=4)
    at qeventloop_x11.cpp:389
#18 0xb6412b55 in QEventLoop::enterLoop (this=0x8139f20) at qeventloop.cpp:198
#19 0xb6412a70 in QEventLoop::exec (this=0x8139f20) at qeventloop.cpp:145
#20 0xb63fae35 in QApplication::exec (this=0xbfd67210) at qapplication.cpp:2758
#21 0x0805c54d in main (argc=927, argv=0x39f) at main.cpp:161
Comment 1 Reinhold Kainhofer 2006-11-02 19:14:14 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 2 Bram Schoenmakers 2006-11-24 20:57:30 UTC
*** Bug 137584 has been marked as a duplicate of this bug. ***
Comment 3 Sergio Martins 2009-05-09 18:33:14 UTC
Working fine in recent kde versions. Can you retest?

Thanks
Comment 4 Allen Winter 2009-05-24 16:26:18 UTC
closing due to lack of response and because the reported version is so old.
Comment 5 Christophe Marin 2010-03-28 20:40:46 UTC
*** Bug 191470 has been marked as a duplicate of this bug. ***