Bug 181266 - Kontact kill by signal 11 when closed when I created an email diffusion list
Summary: Kontact kill by signal 11 when closed when I created an email diffusion list
Status: RESOLVED DUPLICATE of bug 178869
Alias: None
Product: kontact
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: 2009-01-19 08:42 UTC by Richard Van Den Boom
Modified: 2009-01-19 12:17 UTC (History)
1 user (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 Richard Van Den Boom 2009-01-19 08:42:06 UTC
Version:            (using Devel)
Compiler:          4.2.4 Configuré avec: ../gcc-4.2.4/configure --prefix=/usr --enable-shared --enable-languages=ada,c,c++,fortran,java,objc --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --with-arch=i486 --target=i486-slackware-linux --host=i486-slackware-linux
Modèle de thread: posix
version gcc 4.2.4
OS:                Linux
Installed from:    Compiled sources

For most task, Kontact works fine for me. However, if I create in the Contacts section an email distribution list, it will work fine as long as Kontact is running but when I close it, the program will crash with signal 11 and once restarted, no trace will be left of my formerly created distribution list.
I get the following traces during the crash :

Application : Kontact (kontact), signal SIGSEGV
0xb5a8743c in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0xb4bc96d0 (LWP 22903)):
[KCrash Handler]
#5  0xb104c0b6 in Akonadi::Entity::operator= () from /usr/lib/libakonadi-kde.so.4
#6  0xb10873f0 in Akonadi::ItemCreateJob::ItemCreateJob () from /usr/lib/libakonadi-kde.so.4
#7  0xafeac81f in KABC::ResourceAkonadi::Private::createSaveSequence () from /usr/lib/kde4/kabc_akonadi.so
#8  0xafead03b in KABC::ResourceAkonadi::save () from /usr/lib/kde4/kabc_akonadi.so
#9  0xb725157f in KABC::AddressBook::save () from /usr/lib/libkabc.so.4
#10 0xb1c9091e in KABCore::save () from /usr/lib/libkaddressbookprivate.so.4
#11 0xafe9699a in KAddressbookPart::~KAddressbookPart () from /usr/lib/kde4/kaddressbookpart.so
#12 0xb7831569 in Kontact::Plugin::~Plugin () from /usr/lib/libkontactinterfaces.so.4
#13 0xb1ae20ec in KAddressbookPlugin::~KAddressbookPlugin () from /usr/lib/kde4/kontact_kaddressbookplugin.so
#14 0xb784b554 in Kontact::MainWindow::~MainWindow () from /usr/lib/libkontactprivate.so.4
#15 0xb6802c4c in qDeleteInEventHandler () from /usr/lib/qt-4.4.3/lib/libQtCore.so.4
#16 0xb6803edc in QObject::event () from /usr/lib/qt-4.4.3/lib/libQtCore.so.4
#17 0xb5dce6bf in QWidget::event () from /usr/lib/qt-4.4.3/lib/libQtGui.so.4
#18 0xb6124fa5 in QMainWindow::event () from /usr/lib/qt-4.4.3/lib/libQtGui.so.4
#19 0xb6e53224 in KMainWindow::event () from /usr/lib/libkdeui.so.5
#20 0xb6e94e2c in KXmlGuiWindow::event () from /usr/lib/libkdeui.so.5
#21 0xb5d7aecc in QApplicationPrivate::notify_helper () from /usr/lib/qt-4.4.3/lib/libQtGui.so.4
#22 0xb5d7fc18 in QApplication::notify () from /usr/lib/qt-4.4.3/lib/libQtGui.so.4
#23 0xb6d7381d in KApplication::notify () from /usr/lib/libkdeui.so.5
#24 0xb67f4479 in QCoreApplication::notifyInternal () from /usr/lib/qt-4.4.3/lib/libQtCore.so.4
#25 0xb67f5829 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/qt-4.4.3/lib/libQtCore.so.4
#26 0xb67f5a4d in QCoreApplication::sendPostedEvents () from /usr/lib/qt-4.4.3/lib/libQtCore.so.4
#27 0xb681f81f in ?? () from /usr/lib/qt-4.4.3/lib/libQtCore.so.4
#28 0xb526d146 in g_main_context_dispatch () from /usr/X11R6/lib/libglib-2.0.so.0
#29 0xb52704f3 in ?? () from /usr/X11R6/lib/libglib-2.0.so.0
#30 0x090db0e8 in ?? ()
#31 0x00000000 in ?? ()


All my adress book has been switched to Akonadi, and the data is stored in an Akonadi dir in my home dir.
Contacts appear correctly in the Contacts section and new can be added, so accessing the database doesn't seem to be an issue.
Comment 1 Dario Andres 2009-01-19 12:17:25 UTC

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