[Bug 173432] New: Automatic calender (Korganizer) update leads to Kontact crash

[Ralph Moenchmeyer]

http://bugs.kde.org/show_bug.cgi?id=173432

           Summary: Automatic calender (Korganizer) update leads to Kontact
                    crash
           Product: kontact
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: rm at anracon.de


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 ?? ()


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.