Bug 235202

Summary: Unable to Add new Contact
Product: [Applications] korganizer Reporter: Emmett Culley <lst_manage>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 4.4.1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Emmett Culley 2010-04-23 19:39:56 UTC
Application: kontact (4.4.1)
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
Operating System: Linux 2.6.30.10-105.2.23.fc11.x86_64 x86_64
Distribution: "Fedora release 11 (Leonidas)"

-- Information about the crash:
When adding a new contact, I am required to select the address book to associate to.  There is non, and the only option offered is to cancel.  I've been using this program for years, and this latest version is so problematic and buggy, I have to restart it, 10 times a day for other problems we reported.  I can't wait for the new release.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  QListData::begin (this=<value optimized out>) at /usr/include/QtCore/qlist.h:93
#6  QList<KCal::Incidence*>::contains (this=<value optimized out>) at /usr/include/QtCore/qlist.h:757
#7  KCal::ListBase<KCal::Incidence>::removeRef (this=<value optimized out>) at /usr/src/debug/kdepimlibs-4.4.1/kcal/listbase.h:118
#8  KCal::Incidence::removeRelation (this=<value optimized out>) at /usr/src/debug/kdepimlibs-4.4.1/kcal/incidence.cpp:529
#9  0x00007f9bc8a99497 in KCal::Incidence::~Incidence (this=0x1a17e10, __in_chrg=<value optimized out>) at /usr/src/debug/kdepimlibs-4.4.1/kcal/incidence.cpp:201
#10 0x00007f9bc8a9d2eb in KCal::Event::~Event (this=0x1a17e10, __in_chrg=<value optimized out>) at /usr/src/debug/kdepimlibs-4.4.1/kcal/event.cpp:79
#11 0x00007f9bc8abff0f in qDeleteAll<QHash<QString, KCal::Event*>::const_iterator> (end=<value optimized out>, begin=<value optimized out>) at /usr/include/QtCore/qalgorithms.h:322
#12 qDeleteAll<QHash<QString, KCal::Event*> > (end=<value optimized out>, begin=<value optimized out>) at /usr/include/QtCore/qalgorithms.h:330
#13 KCal::CalendarLocal::deleteAllEvents (end=<value optimized out>, begin=<value optimized out>) at /usr/src/debug/kdepimlibs-4.4.1/kcal/calendarlocal.cpp:212
#14 0x00007f9bc8abfc0b in KCal::CalendarLocal::close (this=0x17f68e0) at /usr/src/debug/kdepimlibs-4.4.1/kcal/calendarlocal.cpp:163
#15 0x0000003096e0e342 in KRES::Resource::close (this=0x17f39c0) at /usr/src/debug/kdepimlibs-4.4.1/kresources/resource.cpp:141
#16 0x00007f9bc8b1a095 in KCal::CalendarResources::close (this=0x17e52a0) at /usr/src/debug/kdepimlibs-4.4.1/kcal/calendarresources.cpp:362
#17 0x00007f9bc8b1a3dc in KCal::CalendarResources::~CalendarResources (this=0x284a7a0, __in_chrg=<value optimized out>) at /usr/src/debug/kdepimlibs-4.4.1/kcal/calendarresources.cpp:259
#18 0x00007f9bbc1cdc15 in KOrg::StdCalendar::~StdCalendar (this=0x284a7a0, __in_chrg=<value optimized out>) at /usr/src/debug/kdepim-4.4.1/korganizer/stdcalendar.cpp:109
#19 0x00007f9bbc1cf457 in K3StaticDeleter<KOrg::StdCalendar>::destructObject (this=0x7f9bbc3d08e0) at /usr/include/kde4/k3staticdeleter.h:174
#20 0x0000003097669e8c in K3StaticDeleterPrivate::deleteStaticDeleters () at /usr/src/debug/kdelibs-4.4.1/kde3support/kdecore/k3staticdeleter.cpp:56
#21 0x000000308fd66fa6 in qt_call_post_routines () at kernel/qcoreapplication.cpp:201
#22 0x00000030919b4c28 in QApplication::~QApplication (this=0x7fff27dcbd20, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1016
#23 0x0000000000403d5c in ~KontactApp (this=<value optimized out>, __in_chrg=<value optimized out>) at /usr/src/debug/kdepim-4.4.1/kontact/src/main.cpp:67
#24 main (this=<value optimized out>, __in_chrg=<value optimized out>) at /usr/src/debug/kdepim-4.4.1/kontact/src/main.cpp:227
Warning: the current language does not match this frame.

Possible duplicates by query: bug 231840, bug 230733, bug 229259.

Reported using DrKonqi
Comment 1 Christophe Marin 2010-09-23 11:01:05 UTC
*** Bug 252084 has been marked as a duplicate of this bug. ***
Comment 2 Christophe Marin 2011-01-15 14:35:29 UTC

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