Bug 173432

Summary: Automatic calender (Korganizer) update leads to Kontact crash
Product: [Applications] kontact Reporter: Ralph Moenchmeyer <rm>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: christophe, franke.daniel, rm
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ralph Moenchmeyer 2008-10-24 15:29:21 UTC 
Version:           3.5.9 (using KDE 3.5.10)
OS:                Linux
Installed from:    SuSE RPMs

This morning I updated KDE 3.5.10  to the latest version via the rpms from the KDE repository of Opensuse. I am using Opensuse 10.3. The KDE version is 3.5.10 "release 28.1". 
Kontact interacts with an OX5 Open-Xchange server (commercial version, SP4 U1). 
 
I now get permanent crashes of Kontact when the calender (Korganizer) is open (!) as the active page/sub-application of Kontact and when an update/synchronization of the calendar entries is performed with the groupware server. The data update process itself seems to initiate and maybe finalizes, but any subsequent mouse click into the Kontact application triggers the crash. The crash also happens when you run Korganizer as a standalone application. 

The crash occurs after any automatic update/synchronization processes of the calendar with the groupware server (in my case Openexchange OX5). (I have set a certain period for automatic reloads from the server; automatic saving for new calendar entries is deactivated). 
However, a crash also occurs when you click on the ox Kalendar ressource (reload) and thus initiate a manual data download from the server. The bug therefore can easily be reproduced.  
 
No crash occurs when any other application of Kontact (e.g. Kmail) is open during the regular update processes with the groupware server. 

So I think this is a Kontact/Korganizer bug which seems to be specific for the present KDE 3.5.10 release:   

For comparison I tested the automatic update behaviour of Kontact /Kalender/Korganizer of a previous KDE version - version 3.5.9 "release 53.4". There everything works flawless and smooth. 
  
Below you find the crash report : 

KDE crash report:
-----------------------

Überprüfung der Systemkonfiguration beim Start deaktiviert.

 [?1034h(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(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 0x2b64cf55e770 (LWP 6332)]
[KCrash handler]
#5  0x00002b64c53cd06e in KOAgendaItem::paintEvent ()
   from /opt/kde3/lib64/libkorganizer.so.1
#6  0x00002b64c72ea9d7 in QWidget::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#7  0x00002b64c72629dd in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#8  0x00002b64c72636be in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#9  0x00002b64c6a4ab2d in KApplication::notify ()
   from /opt/kde3/lib64/libkdecore.so.4
#10 0x00002b64c7238cf1 in QWidget::repaint ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#11 0x00002b64c72640d5 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#12 0x00002b64c72184cb in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#13 0x00002b64c7277253 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#14 0x00002b64c7277102 in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#15 0x000000000040aae8 in QWidget::setUpdatesEnabled ()
#16 0x00002b64c7ccfb54 in __libc_start_main () from /lib64/libc.so.6
#17 0x000000000040a8c9 in QWidget::setUpdatesEnabled ()
#18 0x00007fffe5a2b5a8 in ?? ()
#19 0x0000000000000000 in ?? ()
Comment 1 Ralph Moenchmeyer 2008-10-24 16:28:57 UTC 
I should add the following: I meanwhile installed the additional kdepim3-time-management tools. 

After that the crash sometimes does not occur directly after the synchro with the server but when you double-click to insert a new entry into your Kontact calendar.

Additionally, a crash sometimes (!) also occurs when Kmail is open and you switch to the Korganizer calendar after an automatic calendar update has been performed. 

To summarize it: Sooner or later an activity on the calendar or a switch to the calendar will lead to a Kontact crash after an update of data has been performed via a reload from a groupware server.
Comment 2 Ralph Moenchmeyer 2008-10-24 19:29:34 UTC 
I installed KDE 4.1 for Fun on another system. 

The problem described above does not exist for KDE 4.1 Kontact on the other machine. So this is an indication that the bug might be specific for KDE 3.5.10 - rel. 28.1.   

I shall install KDE 4.1 on the same system as KDE 3.5.10 this evening and check again.
Comment 3 Ralph Moenchmeyer 2008-10-25 02:58:45 UTC 
Meanwhile, I have installed KDE 4.1 in parallel to KDE 3.5.10 on the same system (x86_64 architecture). 
The bug does not occur for occur for the KDE 4.1 Kontact/Korganizer within its KDE 4.1 environment. 

However, when I start the KDE 3.5.10 Kontact/Korganizer within the KDE 4.1 environment crashes do occur as well as in the original KDE 3.5.10 environment. So, there is a bug in the latest Kontact version for KDE 3.5.10.
Comment 4 Daniel Franke 2008-11-28 16:23:02 UTC 
After importing a remote calendar, I got this backtrace on application restart (probably the same as above, but more detailed):

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb58b96d0 (LWP 27764)]
[New Thread 0xb33b7b90 (LWP 27768)]
[New Thread 0xb3bb8b90 (LWP 27767)]
[New Thread 0xb43b9b90 (LWP 27766)]
[New Thread 0xb4bbab90 (LWP 27765)]
[KCrash handler]
#6  0xb7f0a424 in __kernel_vsyscall ()
#7  0xb58e7101 in raise () from /lib/libc.so.6
#8  0xb58e88e8 in abort () from /lib/libc.so.6
#9  0xb591dcbb in __libc_message () from /lib/libc.so.6
#10 0xb5923a00 in malloc_printerr () from /lib/libc.so.6
#11 0xb59256f9 in free () from /lib/libc.so.6
#12 0xb5ad5111 in operator delete ()
   from /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6
#13 0xb65d11ad in QGArray::deleteData (this=0xbfb25128, p=0x8e17ec0)
    at tools/qgarray.cpp:829
#14 0xb553f7a2 in KOAgendaItem::paintEvent ()
   from /usr/kde/3.5/lib/libkorganizer.so.1
#15 0xb62b842b in QWidget::event (this=0x8f04e70, e=0xbfb25640)
    at kernel/qwidget.cpp:4783
#16 0xb6202de3 in QApplication::internalNotify (this=0xbfb25b78, 
    receiver=0x8f04e70, e=0xbfb25640) at kernel/qapplication.cpp:2638
#17 0xb62059b2 in QApplication::notify (this=0xbfb25b78, receiver=0x8f04e70, 
    e=0xbfb25640) at kernel/qapplication.cpp:2526
#18 0xb6aa7c64 in KApplication::notify (this=0xbfb25b78, receiver=0x8f04e70, 
    event=0xbfb25640) at kapplication.cpp:550
#19 0xb618cafd in QApplication::sendSpontaneousEvent (receiver=0x8f04e70, 
    event=0xbfb25640) at kernel/qapplication.h:502
#20 0xb6179c4c in QETWidget::translatePaintEvent (this=0x8f04e70, 
    event=0xbfb259d8) at kernel/qapplication_x11.cpp:5649
#21 0xb6189bb4 in QApplication::x11ProcessEvent (this=0xbfb25b78, 
    event=0xbfb259d8) at kernel/qapplication_x11.cpp:3500
#22 0xb61a27ae in QEventLoop::processEvents (this=0x8865b40, flags=4)
    at kernel/qeventloop_x11.cpp:195
#23 0xb6220c01 in QEventLoop::enterLoop (this=0x8865b40)
    at kernel/qeventloop.cpp:201
#24 0xb6220a22 in QEventLoop::exec (this=0x8865b40)
    at kernel/qeventloop.cpp:148
#25 0xb6204aa7 in QApplication::exec (this=0xbfb25b78)
    at kernel/qapplication.cpp:2761
#26 0x0805d366 in main ()
Comment 5 Daniel Franke 2008-11-28 16:23:45 UTC 
Should have mentioned, backtrace in comment #4 is from KDE-3.5.10.
Comment 6 Christophe Marin 2008-12-08 21:02:08 UTC 

*** This bug has been marked as a duplicate of bug 170669 ***