Bug 213179 - The kdepim application crashed on closing.
Summary: The kdepim application crashed on closing.
Status: RESOLVED DUPLICATE of bug 177862
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-05 01:24 UTC by Jim Hitch
Modified: 2009-11-06 02:27 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Hitch 2009-11-05 01:24:26 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
As above. This happens half the time I close the application.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  QBasicAtomicInt::ref (this=0xa39cd70) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#7  QString (this=0xa39cd70) at /usr/include/qt4/QtCore/qstring.h:712
#8  KCal::IncidenceBase::uid (this=0xa39cd70) at ../../kcal/incidencebase.cpp:185
#9  0x019ef559 in removeIncidenceFromMultiHashByUID<KCal::Event*> (container=<value optimized out>, key=<value optimized out>, uid=...) at ../../kcal/calendarlocal.cpp:93
#10 0x019f26e0 in KCal::CalendarLocal::incidenceUpdated (this=0x9ddcbb0, incidence=0xa3b50d8) at ../../kcal/calendarlocal.cpp:394
#11 0x019bd23b in KCal::IncidenceBase::updated (this=0xa3b50d8) at ../../kcal/incidencebase.cpp:480
#12 0x019c0610 in KCal::Incidence::setRelatedToUid (this=0xa3b50d8, relatedToUid=...) at ../../kcal/incidence.cpp:488
#13 0x019c1766 in KCal::Incidence::setRelatedTo (this=0xa3b50d8, incidence=0x0) at ../../kcal/incidence.cpp:511
#14 0x019c4390 in ~Incidence (this=0xa3a18f8, __in_chrg=<value optimized out>) at ../../kcal/incidence.cpp:201
#15 0x019c8f5d in ~Event (this=0xa3a18f8, __in_chrg=<value optimized out>) at ../../kcal/event.cpp:79
#16 0x019ef3b6 in qDeleteAll<QList<KCal::Incidence*>::const_iterator> (this=0x9ddcbb0) at /usr/include/qt4/QtCore/qalgorithms.h:350
#17 qDeleteAll<KCal::ListBase<KCal::Incidence> > (this=0x9ddcbb0) at /usr/include/qt4/QtCore/qalgorithms.h:358
#18 KCal::ListBase<KCal::Incidence>::clearAll (this=0x9ddcbb0) at ../../kcal/listbase.h:105
#19 KCal::CalendarLocal::close (this=0x9ddcbb0) at ../../kcal/calendarlocal.cpp:171
#20 0x01a494e8 in KCal::ResourceCached::doClose (this=0x9d8a7a8) at ../../kcal/resourcecached.cpp:878
#21 0x00381727 in KRES::Resource::close (this=0x9d8a7a8) at ../../kresources/resource.cpp:141
#22 0x01a51465 in KCal::CalendarResources::close (this=0x9dd9838) at ../../kcal/calendarresources.cpp:350
#23 0x01a517d4 in ~CalendarResources (this=0x9dd9838, __in_chrg=<value optimized out>) at ../../kcal/calendarresources.cpp:247
#24 0x01dc5013 in ~StdCalendar (this=0x9dd9838, __in_chrg=<value optimized out>) at ../../korganizer/stdcalendar.cpp:112
#25 0x01dc6d5f in K3StaticDeleter<KOrg::StdCalendar>::destructObject (this=0x1dc90d8) at /usr/include/k3staticdeleter.h:174
#26 0x0324e104 in K3StaticDeleterPrivate::deleteStaticDeleters () at ../../kde3support/kdecore/k3staticdeleter.cpp:56
#27 0x007dfc00 in qt_call_post_routines () at kernel/qcoreapplication.cpp:163
#28 0x00f27ba8 in ~QApplication (this=0xbfa0e5d4, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:971
#29 0x00c3f11a in ~KApplication (this=0xbfa0e5d4, __in_chrg=<value optimized out>) at ../../kdeui/kernel/kapplication.cpp:904
#30 0x00c46588 in ~KUniqueApplication (this=0xbfa0e5d4, __in_chrg=<value optimized out>) at ../../kdeui/kernel/kuniqueapplication.cpp:372
#31 0x0804b571 in ~KontactApp (argc=1, argv=0xbfa0e7f4) at ../../../kontact/src/main.cpp:67
#32 main (argc=1, argv=0xbfa0e7f4) at ../../../kontact/src/main.cpp:221

Reported using DrKonqi
Comment 1 Dario Andres 2009-11-06 02:27:16 UTC
Merging with bug 177862. Thanks

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