Version: 3.5.5 (using KDE 3.5.5 "release 39.1" , openSUSE ) Compiler: Target: i586-suse-linux OS: Linux (i686) release 2.6.16.21-0.25-smp In short: Calendar accessed through kontact corrupts (some) recurring events and the next time I run kontact and try to open the calendar kontact crashes. Using only korganiser there's no problem. (backtrace in the end) Longer story: If I have recurring events and open calendar from kontact those events get corrupted. E.g., an event originally dated to begin and end on 11.11. (last week) and then recurring weekly changes to begin in 18.11. (this week's recurrence) and to end in 11.11. (the original date) and the last weeks event is no longer shown. The time of the event is not changed, only the dates. Also, this only seems to affect currently recurring events but not the ones in the past. Now, the next time I open kontact and try to open the calendar, kontact crashes almost always. On few occasions I was able to open the calendar again and then it shows the events corrupted as described above. I couldn't find out on what circumstances kontact did not crash. However, if I use only korganiser to access the calender and not kontact, there doesn't appear to be any problems of this sort. Backtrace of the crash: System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240697168 (LWP 14838)] [New Thread -1280750688 (LWP 14842)] [New Thread -1272357984 (LWP 14841)] [New Thread -1263965280 (LWP 14840)] [New Thread -1255572576 (LWP 14839)] [KCrash handler] #5 0xb2f34a6d in KOAgendaItem::paintEvent () from /opt/kde3/lib/libkorganizer.so.1 #6 0xb6d03263 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #7 0xb6c6b547 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #8 0xb6c6c339 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #9 0xb7326e03 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #10 0xb6bfe6bd in QETWidget::translatePaintEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #11 0xb6c0a47f in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #12 0xb6c1a68a in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #13 0xb6c82368 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #14 0xb6c821fe in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #15 0xb6c6b0ff in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0x08058c02 in main ()
These are two separate issues. The issue with recurring events is already solved in SVN and thus for KDE 3.5.6. I have no idea why it would crash though. It looks really similar to the crash in bug 128659.
This really seems to have been resolved a long time ago so no reason to keep this report hanging around here...