Bug 100816 - Kontact crashed after creating an appointment
Summary: Kontact crashed after creating an appointment
Status: RESOLVED DUPLICATE of bug 112108
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-04 15:30 UTC by Andreas Gungl
Modified: 2009-03-23 09:31 UTC (History)
3 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 Andreas Gungl 2005-03-04 15:30:09 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc version 3.3.4 (pre 3.3.5 20040809)
OS:                Linux (i686) release 2.6.8-24.11-default

Well, I added an event as uncounted times before, but Kontact crashed this times. I'm using ressources on a Kolab 2 server via DIMAP, some shared folders are installed as well. However I don't think that this might be the cause of the crash.

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1106018336 (LWP 5059)]
[KCrash handler]
#7  0x416f9ffd in QScrollView::verticalScrollBar ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0x42edc495 in KDGanttCanvasView::qt_invoke (this=0x894dbf8, _id=68, 
    _o=0xbfffe660) at qucom_p.h:388
#9  0x415df31e in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x415df94d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x42ed7e58 in KDTimeTableWidget::heightComputed (this=0x8947618, t0=54)
    at qmetaobject.h:261
#12 0x42ed7ec3 in KDTimeTableWidget::computeHeight (this=0x8947618)
    at KDGanttViewSubwidgets.cpp:181
#13 0x42edbffc in KDTimeTableWidget::updateMyContent (this=0x8947618)
    at KDGanttViewSubwidgets.cpp:599
#14 0x42eb6443 in KDGanttView::setUpdateEnabled (this=0x89b3338, enable=true)
    at KDGanttView.cpp:231
#15 0x42e4fbf4 in KOEditorFreeBusy::slotInsertFreeBusy (this=0x88b3620, 
    fb=0x8a36078, email=@0x8a2ee68) at koeditorfreebusy.cpp:432
#16 0x42e4fe1e in KOEditorFreeBusy::qt_invoke (this=0x88b3620, _id=46, 
    _o=0xbfffe890) at qucom_p.h:312
#17 0x415df31e in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x42e853f9 in FreeBusyManager::freeBusyRetrieved (this=0x88d1420, 
    t0=0x8a36078, t1=@0xbfffe9c0) at freebusymanager.moc:232
#19 0x42e89f25 in FreeBusyManager::retrieveFreeBusy (this=0x88d1420, 
    email=@0xbfffe9c0) at freebusymanager.cpp:340
#20 0x42e4db68 in KOEditorFreeBusy::timerEvent (this=0x88b3620, 
    event=0xbfffee50) at person.h:72
#21 0x415dfd01 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x416153df in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x4157cbaf in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x4157e773 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x4111e59a in KApplication::notify (this=0xbffff090, receiver=0x88b3620, 
    event=0xbfffee50) at kapplication.cpp:549
#26 0x4157135c in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x4152a156 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0x41594b41 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x41594986 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x4157e63f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0x08059122 in main (argc=1, argv=0xbffff314) at main.cpp:156
Comment 1 Daniel Molkentin 2005-06-09 15:27:16 UTC
Looks like a bug in KDGanttView.
Comment 2 Reinhold Kainhofer 2006-11-02 19:34:30 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 3 Allen Winter 2008-10-21 01:43:47 UTC
I know this is very old.
Andreas, can I close this?
Comment 4 Christophe Marin 2008-11-17 21:52:35 UTC
Isn't it a dup of bug 112108 ? 
Comment 5 Sergio Martins 2009-03-23 09:31:21 UTC
Yes, probably a dup of bug 112108. Also, I haven't seen this old crash in KDE4.

Closing then.

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