Bug 199164

Summary:	crash when starting again after adding old addressbook resources and then trying to add an address
Product:	[Applications] kontact	Reporter:	Arne Babenhauserheide <arne_bab>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra, christophe, deblauwetom
Priority:	HI
Version:	4.3
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Arne Babenhauserheide 2009-07-06 16:23:10 UTC

Application that crashed: kontact
Version of the application: 4.3.0 rc1
KDE Version: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1))
Qt Version: 4.5.2
Operating System: Linux 2.6.29-hh2 x86_64

What I was doing when the application crashed:
I went into addressbook and enabled the old resources, because the Akonadi compatiblility resoruce didn't show my contacts. 

Then I switched back to kmail and added a contact. 

The first addition worked (but slow), but the second froze kontact and I finally closed the window. 

When I tried to start kontact again it crashed. 

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#4  0x00007f676959d878 in KABC::AddressBook::loadingHasFinished () from /usr/lib64/libkabc.so.4
#5  0x00007f676a930faa in KPIM::KAddrBookExternal::addAddressee () from /usr/lib64/libkdepim.so.4
#6  0x00007f676a932510 in KPIM::KAddrBookExternal::addEmail () from /usr/lib64/libkdepim.so.4
#7  0x00007f6754983faa in KMMailtoAddAddrBookCommand::execute () from /usr/lib64/libkmailprivate.so.4
#8  0x00007f675497d6fa in KMCommand::slotPostTransfer () from /usr/lib64/libkmailprivate.so.4
#9  0x00007f675498728e in KMCommand::qt_metacall () from /usr/lib64/libkmailprivate.so.4
#10 0x00007f6765fb0f15 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#11 0x00007f675497a94e in KMCommand::messagesTransfered () from /usr/lib64/libkmailprivate.so.4
#12 0x00007f6754996128 in KMCommand::transferSelectedMsgs () from /usr/lib64/libkmailprivate.so.4
#13 0x00007f675499634e in KMCommand::slotStart () from /usr/lib64/libkmailprivate.so.4
#14 0x00007f67549872a2 in KMCommand::qt_metacall () from /usr/lib64/libkmailprivate.so.4
#15 0x00007f6765fb0f15 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#16 0x00007f6765fb72ef in ?? () from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007f6765fad843 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4
#18 0x00007f6766ae9b3d in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4
#19 0x00007f6766af240a in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4
#20 0x00007f6767863bbb in KApplication::notify () from /usr/lib64/libkdeui.so.5
#21 0x00007f6765f9f033 in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4
#22 0x00007f6765fc6eee in ?? () from /usr/lib64/qt4/libQtCore.so.4
#23 0x00007f6765fc3c8d in ?? () from /usr/lib64/qt4/libQtCore.so.4
#24 0x00007f67615e8fe1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0x00007f67615ec6bd in ?? () from /usr/lib/libglib-2.0.so.0
#26 0x00007f67615ec87b in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0x00007f6765fc3bff in QEventDispatcherGlib::processEvents () from /usr/lib64/qt4/libQtCore.so.4
#28 0x00007f6766b6ee6f in ?? () from /usr/lib64/qt4/libQtGui.so.4
#29 0x00007f6765f9da32 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4
#30 0x00007f6765f9dbcc in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4
#31 0x00007f6765f9fbc4 in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4
#32 0x0000000000404b51 in _start ()

This bug may be a duplicate of or related to bug 178986

Reported using DrKonqi

Comment 1 Dario Andres 2009-07-07 01:28:46 UTC

This seems related to bug 178781 / bug 141766
Thanks

Comment 2 Christophe Marin 2009-07-09 12:05:17 UTC

*** Bug 199402 has been marked as a duplicate of this bug. ***

Comment 3 Christophe Marin 2010-03-28 20:11:47 UTC


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